When using the 'manywarnings' module for the first time, I looked at an
example use, such as this one from grep/configure.ac:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# This, $nw, is the list of warnings we disable.
nw="$nw -Wvla"# sup
Paul Eggert wrote on 2023-05-27:
> If there are other ways to generate warnings to find bugs that are worth
> the trouble of pacifying GCC, then it'd be helpful to use those ways
> too. But plain 'gcc -Wall' is not one of those ways.
> ...
> I ... update the manywarnings module accordingly. This
I did:
> (error): Define as a macro that explicitly invokes exit().
> (error_at_line): Likewise.
Oops. That patch broke the library namespacing via config.h. Namely,
when a package uses a config.h definition such as
#define error libgettextpo_error
the intent is that the Gnulib modul
In GNU gettext, I see these warnings (with gcc 12):
libtextstyle/lib/tparm.c:350:19: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscarded-qualifiers]
libtextstyle/lib/tparm.c:432:19: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscar
This patch adds comments, how to avoid excessive compilation times due to
"gcc -fanalyzer".
2023-06-04 Bruno Haible
uniname/uniname: Add comments.
* modules/uniname/uniname (Makefile.am): Explain how to work around a
GCC bug.
diff --git a/modules/uniname/uniname b/mod
In GNU gettext, with gcc 13, I see this warning:
gettext-tools/gnulib-lib/uniname/uniname.c:295:42: warning: format '%d' expects
argument of type 'int', but argument 3 has type 'ucs4_t' {aka 'unsigned int'}
[-Wformat=]
This patch fixes it. The other patch fixes some comments.
2023-06-04 Brun
