This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/51388] Configure failure to detect unsupported warning options for non-bootstrap builds (including cross builds)
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 02 Dec 2011 14:51:14 +0000
- Subject: [Bug bootstrap/51388] Configure failure to detect unsupported warning options for non-bootstrap builds (including cross builds)
- Auto-submitted: auto-generated
- References: <bug-51388-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51388
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011-12-02
CC| |jsm28 at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-12-02 14:51:14 UTC ---
I think the issue is that we allow random -Wno- as argument, but not
positive variants. Trunk:
> ./xgcc -B. -c t.c -Wno-foo
> ./xgcc -B. -c t.c -Wfoo
xgcc: error: unrecognized command line option '-Wfoo'
that's probably deliberate. So the bug is that we check for
-Wno-narrowing instead of -Wnarrowing.
Now, the question is why we don't consistently error in 4.3 ...
I see
> gcc-4.3 -c -Wno-narrowing t.c -DHAVE_ARG
cc1: error: unrecognized command line option "-Wno-narrowing"
with FSF GCC 4.3.6. So, are you sure this isn't behavior caused by
vendor patches? (openSUSE GCC 4.3 also works)
Still the behavior of warning for -Wno- changed appearantly. Joseph?