GNU bug report logs - #70889
29.3; GCC14.1 MinGW compilation error

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Cyril Arnould <cyril.arnould <at> outlook.com>, Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 70889 <at> debbugs.gnu.org
Subject: bug#70889: 29.3; GCC14.1 MinGW compilation error
Date: Sun, 12 May 2024 20:16:09 +0300

> Date: Sun, 12 May 2024 18:21:56 +0200
> Cc: 70889 <at> debbugs.gnu.org
> From: Cyril Arnould <cyril.arnould <at> outlook.com>
> 
>  > Which also says that turning these back into warnings is as simple as
>  > adding -Wno-error=implicit-function-declaration.  Can you try that
>  > (via CFLAGS=... setting when you run the configure script)?
> 
> Oh, I hadn't seen that. Yep, with this flag the configure script's
> errors turn into warnings and subsequent the compilation error is
> gone.

Then I guess we should use that on MS-Windows when running the
configure script.  Paul, is there a better way.

> Only the GCC internal compilation error remains, but it seems that
> adding the '-fno-fold-mem-offsets' flag provides a workaround for
> that. FYI.

The fact that GCC reports an ICE for a perfectly valid C code means
you should not yet use that version of GCC to build programs that are
supposed to be reliable.  My recommendation is to wait until GCC 14.2
is released, and in the meantime stay with GCC 13.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.