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 c/65403] New: -Wno-error=<not implemented> is an error Date: Thu, 12 Mar 2015 14:36:00 -0000 [thread overview] Message-ID: <bug-65403-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65403 Bug ID: 65403 Summary: -Wno-error=<not implemented> is an error Product: gcc Version: 5.0 Status: UNCONFIRMED Keywords: diagnostic Severity: enhancement Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org If you want to silence warnings you can use -Wno-XXX without caring about whether a compiler implements -WXXX already. This doesn't seem to work with -Wno-error=XXX which errors on unknown XXX. It seems to me that we should treat -W[no-]error=XXX the same as -Wno-XXX for unknown XXX as it certainly will enable/disable errors for the warning XXX both if present or not present (no warnings anyway). > gcc-5 -Wall -Werror -Wno-error=logical-not-parentheses -S t.c > gcc-4.8 -Wall -Werror -Wno-error=logical-not-parentheses -S t.c cc1: error: -Werror=logical-not-parentheses: no option -Wlogical-not-parentheses > gcc-5 -Wno-error=foo -S t.c cc1: error: -Werror=foo: no option -Wfoo
next reply other threads:[~2015-03-12 14:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-12 14:36 rguenth at gcc dot gnu.org [this message] 2015-03-12 14:38 ` [Bug c/65403] " rguenth at gcc dot gnu.org 2015-03-12 16:09 ` manu at gcc dot gnu.org 2015-03-12 17:10 ` manu at gcc dot gnu.org 2021-08-12 16:48 ` alexhenrie24 at gmail dot com
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-65403-4@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).