public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/51806] -flto ignores -Werror Date: Tue, 10 Jan 2012 10:04:00 -0000 [thread overview] Message-ID: <bug-51806-4-567DbKTkkb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51806-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51806 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-01-10 CC| |jsm28 at gcc dot gnu.org AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-10 10:03:17 UTC --- Confirmed. It seems that -Werror is a C-family frontend specific option, despite being annotated as 'common'. Only c_common_handle_option has case OPT_Werror: global_dc->warning_as_error_requested = value; break; and thus properly adjusts the diagnostic machinery of the middle-end. But -Werror=... seems to be handled fine (thus, in your case -Werror=uninitialized). That seems inconsistent at least. It looks like the OPT_Werror handling above should move to common_handle_option instead. Joseph?
next prev parent reply other threads:[~2012-01-10 10:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-10 1:28 [Bug lto/51806] New: " DeusExSophismata at gmail dot com 2012-01-10 10:04 ` rguenth at gcc dot gnu.org [this message] 2012-01-10 16:29 ` [Bug lto/51806] " rguenth at gcc dot gnu.org 2012-01-10 16:32 ` rguenth 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-51806-4-567DbKTkkb@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: linkBe 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).