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: 20 Feb 2007 23:22:00 -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 #7 from manu at gcc dot gnu dot org 2007-02-20 23:21 -------
(In reply to comment #6)
> I think the point Ian was trying to make with (3) was simply that it doesn't
> matter whether you choose to implement the reports of unknown -Wno-* (ie (2))
> using the existing warning mechanism or by just printing to stderr. So it isn't
> a separate thing that needs to be done.
>
OK. I misread it, thanks for the clarification. So, nothing to be done for (3)
since there is already a mechanism to report unknown options.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28322