public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/34695] Preprocessor warning->error conversion from -Werror is silent Date: Mon, 07 Jan 2008 20:56:00 -0000 [thread overview] Message-ID: <20080107200847.31682.qmail@sourceware.org> (raw) In-Reply-To: <bug-34695-8392@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from tromey at gcc dot gnu dot org 2008-01-07 20:08 ------- I agree this is a bug. I think this patch is insufficient. For best results I think that libcpp and diagnostic.c should agree on whether the "warnins being treated as errors" message has been emitted. One way to do this would be to finally switch libcpp to emit all errors via diagnostic.c. Though I suppose that, even if we do this, we may still need something like this patch for other users of libcpp. -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2008-01-07 20:08:47 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34695
next prev parent reply other threads:[~2008-01-07 20:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-06 22:31 [Bug preprocessor/34695] New: " ed at catmur dot co dot uk 2008-01-06 23:19 ` [Bug preprocessor/34695] " ed at catmur dot co dot uk 2008-01-07 20:56 ` tromey at gcc dot gnu dot org [this message] 2008-01-20 10:00 ` ed at catmur dot co dot uk 2008-01-20 22:31 ` ed at catmur dot co dot uk 2008-01-20 23:16 ` ed at catmur dot co dot uk 2008-01-22 2:45 ` ed at catmur dot co dot uk 2008-01-22 2:47 ` ed at catmur dot co dot uk 2008-01-22 6:07 ` manu at gcc dot gnu dot org 2009-02-11 1:14 ` jsm28 at gcc dot gnu dot org 2009-03-29 22:56 ` jsm28 at gcc dot gnu dot org 2009-03-29 22:59 ` jsm28 at gcc dot gnu dot 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=20080107200847.31682.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: 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).