public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldionne.2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94745] New: No error emitted for unknown -Wno-meow argument Date: Fri, 24 Apr 2020 13:25:24 +0000 [thread overview] Message-ID: <bug-94745-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94745 Bug ID: 94745 Summary: No error emitted for unknown -Wno-meow argument Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldionne.2 at gmail dot com Target Milestone: --- GCC does not diagnose unsupported -Wno-meow command line flags unless another error happens during compilation. For example, the following compiles just fine even though -Wno-foo doesn't exist: $ echo | g++ -xc++ - -Werror -fsyntax-only -Wno-foo <nothing> If, however, another error happens during compilation, the unsupported command-line flag is reported: $ echo '#error' | g++ -xc++ - -Werror -fsyntax-only -Wno-foo <stdin>:1:2: error: #error cc1plus: error: unrecognized command line option '-Wno-foo' [-Werror] cc1plus: all warnings being treated as errors This makes detecting whether GCC supports a given warning flag very challenging in build systems. This issue popped up while trying to support GCC when running the libc++ Standard Library conformance test suite.
next reply other threads:[~2020-04-24 13:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-24 13:25 ldionne.2 at gmail dot com [this message] 2020-04-24 13:34 ` [Bug c++/94745] " redi at gcc dot gnu.org 2020-04-24 13:36 ` redi at gcc dot gnu.org 2020-04-24 17:42 ` rguenth at gcc dot gnu.org 2020-05-04 14:38 ` ldionne.2 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-94745-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).