On Sat, 20 Jun 2009, Ian Lance Taylor wrote: > That said, > I'm perfectly amenable to moving the new warning to -Wextra or just > turning it on only with -Wc++-compat. I don't personally care that > much, actually.
I also agree with Robert's comments that all warnings are about valid C, with -Wall we diagnose what we subjectively feel is dubious coding practice. Not everyone will agree with what -Wall contains, that's not a reason to freeze it. Furthermore I am not impressed by a total of four warnings between binutils and GCC. Those are large packages and not necessarily representative of the average package among a gnu/linux distro. Now if someone does a test and shows that building the world exposes hundreds or even dozens of these warnings, **and** none of them are actual bugs, then I would reevaluate my opinion. Finally, the compromise fallback position should be to move it to -W/-Wextra (like -Wsign-compare in the past). As a dubious coding practice, I don't think we should banish it to only -Wc++-compat. --Kaveh