> On Sat, 20 Jun 2009, H.J. Lu wrote: >> I think it is a bad idea to include it in -Wall. You fixed 3 warnings in >> gcc and I fixed 1 in binutils. If you have thousands of packages in C, >> -Wall may generate hundreds of warnings. It will make gcc 4.5.0 unusable >> to those people. > > A warning is a warning is a warning and hardly should make GCC unusable.
>I propose this: > > (1) if std=c99 or -std=gnu99, include the warning in -Wall > (2) otherwise, include it in -Wextra > Of course, it will always be part of -Wc++-compat. I strongly agree, the last thing GCC needs is more noise on established platforms, and/or false positive warnings -- Greetings (mit freundlichen Grüßen), Brian.
