public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37187] please provide a way to treat -pedantic as warning when using -Werror Date: Sun, 22 Apr 2012 20:03:00 -0000 [thread overview] Message-ID: <bug-37187-4-bvPTy1NpQv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-37187-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37187 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Target|x86_64-linux-gnu | Host|x86_64-linux-gnu | Build|x86_64-linux-gnu | --- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-22 20:03:11 UTC --- In GCC 4.8, you can use -Wno-error=pedantic for any warning that prints -Wpedantic. However, the testcase here does not because of a bug. I will try to fix the bug, but this part of the C FE is quite complex (and it looks ancient...) -pedantic changes something in a global variable and later the pedwarn is conditional on this global variable, so depending on the testcase, the pedwarn may be conditional or not on -pedantic (without passing the correct OPT_ value). Not fun.
next prev parent reply other threads:[~2012-04-22 20:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-37187-4@http.gcc.gnu.org/bugzilla/> 2011-11-18 20:11 ` skunk at iskunk dot org 2012-04-22 20:03 ` manu at gcc dot gnu.org [this message] 2021-07-29 17:26 ` pinskia at gcc dot gnu.org 2008-08-21 13:26 [Bug c/37187] New: " edwintorok at gmail dot com 2008-08-21 13:28 ` [Bug c/37187] " edwintorok at gmail dot com 2008-08-21 16:13 ` manu at gcc dot gnu dot org 2008-08-21 18:05 ` manu at gcc dot gnu dot org 2008-08-22 12:17 ` manu 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=bug-37187-4-bvPTy1NpQv@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).