From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BD2A43858D28; Fri, 6 Jan 2023 04:06:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD2A43858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1672977966; bh=TfglqziNStahwNWA2C2e3nFPMnr0qckSCC9Li+j5ECg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Wt9TK/t5HMZA3tBOIsXK6yK/sW3Yp6KzTLahrsSsNWrgnIm0gltEAhClZcj4FTScL h+98Z4z3rvVzOhcnTp2SbqAQwA2JfzSLPxejKq7Y9LvcTxwnh3Q9bxDxEmMCnbeMcB BSFFQphe6z6TUlqunerIbfs8FYvydbzt+kVUl01E= From: "egallager at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108310] Some warnings that -Wtraditional-conversion causes to be emitted aren't actually controlled by it Date: Fri, 06 Jan 2023 04:06:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: diagnostic, easyhack X-Bugzilla-Severity: trivial X-Bugzilla-Who: egallager at gcc dot gnu.org 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: see_also blocked Message-ID: In-Reply-To: References: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108310 Eric Gallager changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=3D103210 Blocks| |44209 --- Comment #1 from Eric Gallager --- Kinda related to bug 103210, IMO, in that I've uncovered both of them by building my fork of gdb with gcc: https://github.com/cooljeanius/apple-gdb-= 1824 And, they're also both examples of places where warnings in gcc/c/c-typeck.= cc have a "0" for the second argument where they really ought to have an option name instead, as per bug 44209. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D44209 [Bug 44209] [meta-bug] Some warnings are not linked to diagnostics options=