public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51388] Configure failure to detect unsupported warning options for non-bootstrap builds (including cross builds)
Date: Fri, 02 Dec 2011 16:10:00 -0000	[thread overview]
Message-ID: <bug-51388-4-x6D5tWCdOG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51388-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51388

--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-12-02 16:09:57 UTC ---
On Fri, 2 Dec 2011, rguenth at gcc dot gnu.org wrote:

> Still the behavior of warning for -Wno- changed appearantly.  Joseph?

The idea was that if an unknown -Wno- option is passed, but there were no 
warnings, it doesn't matter that we don't know what warnings the -Wno- 
option might have been intended to disable because there were no warnings 
at all for it to disable - so diagnosis of unknown -Wno- options is 
deferred and they are only diagnosed if some other warning (that the 
unknown option might potentially have been intended to disable) is given.


  parent reply	other threads:[~2011-12-02 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 13:33 [Bug bootstrap/51388] New: " steven at gcc dot gnu.org
2011-12-02 14:51 ` [Bug bootstrap/51388] " rguenth at gcc dot gnu.org
2011-12-02 14:53 ` rguenth at gcc dot gnu.org
2011-12-02 14:59 ` stevenb.gcc at gmail dot com
2011-12-02 15:01 ` steven at gcc dot gnu.org
2011-12-02 16:10 ` joseph at codesourcery dot com [this message]
2011-12-02 16:21 ` rguenth at gcc dot gnu.org
2011-12-02 16:49 ` steven at gcc dot gnu.org
2011-12-02 17:00 ` manu at gcc dot gnu.org
2011-12-19 13:13 ` schwab at gcc dot gnu.org
2011-12-20 14:47 ` andreast at gcc dot gnu.org
2011-12-20 15:58 ` schwab@linux-m68k.org
2011-12-20 16:10 ` andreast 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=bug-51388-4-x6D5tWCdOG@http.gcc.gnu.org/bugzilla/ \
    --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).