This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/28322] GCC new warnings and compatibility
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Jan 2007 01:15:53 -0000
- Subject: [Bug other/28322] GCC new warnings and compatibility
- References: <bug-28322-5724@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from manu at gcc dot gnu dot org 2007-01-24 01:15 -------
I agree with most of what you say but, unfortunately, unless someone that can
approve a patch for this also agrees, it is pointless even to think about how
to implement it. Also, bugzilla is not closely followed by GCC maintainers
(except Andrew Pinski, but Andrew is not human, he lives in bugzilla's mind).
You may have better luck in gcc@gcc.gnu.org. (if you get ignored, you may need
to try a few times, though).
I would recommend to raise one point at a time. For example,
1. GCC should ignore unknown -Wno-* options if no other warnings are to
be issued. This is always correct since the only effect of such an
option would be to suppress warnings which might otherwise be
issued. If no warnings are to be issued at all then treating even
an unknown suppression as a no-op is clearly correct.
If you get the appropriate maintainer to agree on this point, I volunteer to
implement it for GCC 4.3 (subject to my free time, but it will be high in my
priority list). You may ever convince the release manager to add it to GCC 4.2
before it is released.
Good luck!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28322