public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/28322] GCC new warnings and compatibility
Date: Tue, 20 Feb 2007 23:22:00 -0000 [thread overview]
Message-ID: <20070220232200.19243.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28322-5724@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2007-02-20 23:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 23:04 [Bug other/28322] New: " debian-gcc at lists dot debian dot org
2006-07-09 10:41 ` [Bug other/28322] " pinskia at gcc dot gnu dot org
2006-10-18 15:11 ` ian at davenant dot greenend dot org dot uk
2007-01-24 1:16 ` manu at gcc dot gnu dot org
2007-02-20 22:24 ` pmaydell at chiark dot greenend dot org dot uk
2007-02-20 22:36 ` manu at gcc dot gnu dot org
2007-02-20 23:15 ` pmaydell at chiark dot greenend dot org dot uk
2007-02-20 23:22 ` manu at gcc dot gnu dot org [this message]
2007-11-16 20:01 ` manu at gcc dot gnu dot org
2007-11-16 21:18 ` ian at davenant dot greenend dot org dot uk
2008-02-25 23:43 ` manu at gcc dot gnu dot org
2008-02-26 1:00 ` manu at gcc dot gnu dot org
2008-02-27 12:35 ` manu at gcc dot gnu dot org
2008-02-27 13:33 ` pmaydell at chiark dot greenend dot org dot uk
2008-02-27 13:43 ` manu at gcc dot gnu dot org
2008-03-01 16:37 ` manu at gcc dot gnu dot org
2008-03-02 15:19 ` manu at gcc dot gnu dot org
2008-03-04 20:30 ` manu at gcc dot gnu dot org
2008-05-05 16:16 ` pinskia at gcc dot gnu dot org
2008-05-05 17:58 ` pmaydell at chiark dot greenend dot org dot uk
2008-06-05 8:32 ` pmaydell at chiark dot greenend dot org dot uk
2008-07-10 3:52 ` doko at gcc dot gnu dot org
2008-07-22 10:00 ` manu at gcc dot gnu dot org
2009-02-10 18:02 ` jakub at gcc dot gnu dot org
2009-02-12 0:25 ` manu at gcc dot gnu dot org
2009-02-12 8:35 ` pmaydell at chiark dot greenend dot org dot uk
2009-12-29 15:35 ` debian-gcc at lists dot debian dot org
2009-12-29 16:18 ` pmaydell at chiark dot greenend dot org dot uk
2009-12-30 1:49 ` manu at gcc dot gnu dot org
2009-12-30 11:13 ` debian-gcc at lists dot debian dot org
2009-12-30 11:19 ` manu at gcc dot gnu dot org
[not found] <bug-28322-4@http.gcc.gnu.org/bugzilla/>
2024-02-26 16:12 ` pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070220232200.19243.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).