On 23/05/2020 07:26, Paul Eggert wrote:
On 5/21/20 4:23 PM, Pádraig Brady wrote:
I just use the default configure, which auto enables gcc warnings for git repo
builds,
and then build with:
make CFLAGS="-march=native -std=gnu11 -g -O3 -fanalyzer" WERROR_CFLAGS=
OK, so you're building with nonstandard warning options. In general we don't
support that sort of thing; although './configure --enable-gcc-warnings' is
supposed to pacify GCC we can't pacify all combinations of compiler options for
all compilers; that would be too much makework for too little benefit (and
sometimes impossible, as compilers can always be picking about something....).
Well I'm not touching WARN_CFLAGS and effectively only adding -fanalyzer above.
The WERROR_CFLAGS= is to keep going to get all warnings for the build.
Note -Wanalyzer... flags are ineffective without -fanalyzer.
Also -Wanalyzer-too-complex (now auto enabled by gnulib) is currently quite
problematic with -fanalyzer.
cheers,
Pádraig
