From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id C58D53893653; Fri, 24 Apr 2020 13:25:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C58D53893653
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587734724;
 bh=l2X+U1UP400jT3NqDz/zqwzp3zMzwIHcdG9nYy+xWEo=;
 h=From:To:Subject:Date:From;
 b=K+KsIt09/oug38L89JGxLvS0N038qtX7dzACq2+4+XtXGlJNHUJvoIQJqmRIvjXwi
 tzVvwLWsJ+6bLDutdvwPPUDXQQcq4Z+xNqFMzQ4qNMw3AedGz71LkrIU1sSaxKuM3F
 uECfDwZJhZoM6teHl1VYIL2rRCqCMKADsdp6q/dw=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ldionne.2 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-94745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2020 13:25:24 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94745

            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 anoth=
er
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 challen=
ging
in build systems. This issue popped up while trying to support GCC when run=
ning
the libc++ Standard Library conformance test suite.=