+2022-09-23 Simon Josefsson <simon@josefsson.org>
+
+ warnings, manywarnings: Doc fixes.
+ * doc/manywarnings.texi (manywarnings): Improve usage instruction.
+ Start list of comments on particular warning flags, based on
+ comment from Paul Eggert <eggert@cs.ucla.edu>.
+ * doc/warnings.texi (warnings): Mention that it is often used with manywarnings.
+
2022-09-21 Paul Eggert <eggert@cs.ucla.edu>
assert-h: suppress clang false alarms
occur often and don't point to mistakes in the code, by adding them to the
@samp{nw} variable, then reconfiguring and recompiling. When warnings point
to real mistakes and bugs in the code, you will of course not disable
-them.
+them but fix your code to silence the warning instead.
There are also many GCC warning options which usually don't point to mistakes
in the code; these warnings enforce a certain programming style. It is a
that it introduces into the @code{gl_MANYWARN_ALL_GCC} macro (and submit your
modification to the Gnulib maintainers :-)), and enjoy the benefits of the
new warnings, while adding the undesired ones to the @samp{nw} variable.
+
+Comments on particular warning flags:
+
+@table @samp
+
+@item -Wsign-compare
+Clang generates too many false alarms with -Wsign-compare, and we don't
+recommend that warning. Programs using Gnulib generally don't enable
+that warning when compiling Gnulib code. If you happen to find a real
+bug with that warning we'd like to know it.
+
+@end table
@section warnings
The @code{warnings} module allows to regularly build a package with more
-GCC warnings than the default warnings emitted by GCC.
+GCC warnings than the default warnings emitted by GCC. It is often used
+indirectly through the @code{manywarnings} module
+(@pxref{manywarnings}).
It provides the following functionality: