This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/31573] -Wall-all to enable all warnings
- From: "fang at csl dot cornell dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Apr 2007 21:24:22 -0000
- Subject: [Bug c++/31573] -Wall-all to enable all warnings
- References: <bug-31573-14407@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from fang at csl dot cornell dot edu 2007-04-14 22:24 -------
Subject: Re: -Wall-all to enable all warnings
> ------- Comment #2 from pinskia at gcc dot gnu dot org 2007-04-14 21:18 -------
> Actually more than that, there are new warnings options each release so really
> if we have this we will get complaints about warnings options get added. so I
> am going to close this as won't fix.
I also don't really see this ever happening because the libstdc++ headers
aren't clean w.r.t. -Weffc++ (if you propose to turn those on too). Even
the man page warns about it. (Vast majority seem to be "non-virtual
destructor in base class" nonsense from my previous attempts.) Even if
fine-grain, source-annotated warning suppressions (__attribute__, etc.)
kick in, *some* of the extra warnings would be a nuisance to work-around,
and extra work for library maintainers. FWIW, -W -Wall has served me
quite well. (-W is -Wextra since 3.4)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573