Re: manywarnings: Overhaul documentation

[Jeffrey Walton]

On Mon, Jun 5, 2023 at 4:26 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 2023-06-04 15:18, Bruno Haible wrote:
>
> > +Do this once with optimizations (@code{CPPFLAGS=-O2}) and once with no
> > +optimizations (@code{CPPFLAGS=-O0} or @code{CPPFLAGS=-ggdb}).
>
> -ggdb shouldn't affect warnings, no?
>
> More generally, the advice shouldn't recommend -O0 specifically; it
> should recommend whatever optimization options typically used. It's
> common to build with './configure --enable-gcc-warnings; make' and debug
> from there, and when one (rarely) compiles with unusual options to debug
> specially one can do something like "make CFLAGS='-ggdb -O0 -DDEBUG'
> WARN_CFLAGS=" or whatever. If this is the practice there's no need to
> worry about -O0 when tuning manywarnings.

-Og is one you may encounter, too. It is supposed to provide a better
debugging experience. However, I noticed symbolic constants, like
#define's, are often missing. To get the symbolic constants, you still
need -g3.

> I installed the attached to make the documentation a bit more general,
> so that it covers this common style too.

Jeff