From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5E1E7394FC20; Mon, 12 Apr 2021 20:06:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5E1E7394FC20 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/55371] [asan] False -Werror=uninitialized Date: Mon, 12 Apr 2021 20:06:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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: component cc resolution bug_status 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2021 20:06:41 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D55371 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Component|sanitizer |bootstrap CC| |msebor at gcc dot gnu.org Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #3 from Martin Sebor --- In a recent build of GCC 11 I count 69 instances of -Wmaybe-uninitialized without sanitization but not one looking like the one in comment #0. I don= 't have a sanitized build handy but the instrumentation injected by the saniti= zers is known to induce false positives, so (I think) GCC builds with -Wno-error=3Dmaybe-uniitialized when sanitization is enabled. There are a = lot of bugs against the warning with small test cases and odds are that one of them captures the essence of this ancient bug if it is, in fact, a bug and if it hasn't disappeared by now. Since there's been no activity on this bug in almost a decade I'm going to resolve this report as WONTFIX. If it's still reproducible please reopen and attach a standalone test case to make it eas= y to reproduce.=