From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7D0213858C3A; Tue, 12 Sep 2023 12:04:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D0213858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1694520270; bh=dPU6a+TMPH5JYIOXzKZMqKnWD5EJjK3jj7+yzZy7vtg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=o2Fd3bgC5whJgn17x7F2J76rE8dEcl6YKIgTc4/8/bqBOOCkPiDpt/VN8jVxP3504 m0PYHxhdQ1G0oSP31PWsLgkigqVYepWdlaiR4k4ZUcw9jSUSKhhmguhx0QzVdWMX5E d/WTMH/buRYT9Rrg74QXRKbcRc6wnI49fs1VD8H4= From: "jakub1miernik at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105562] [12 Regression] std::function::_M_invoker may be used uninitialized in std::regex move with -fno-strict-aliasing Date: Tue, 12 Sep 2023 12:04:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 12.1.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub1miernik at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D105562 Jakub Miernik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub1miernik at gmail dot= com --- Comment #22 from Jakub Miernik --- (In reply to Uri Simchoni from comment #21) > (In reply to Richard Biener from comment #18) > > (In reply to Sven Hesse from comment #17) > > > I still get this with gcc 12.2.0 (Gentoo 12.2.0 p9), but only when co= mpiling > > > with (at least with) -O1 -fsanitize=3Daddress, in addition to any war= ning flag > > > that enables -Wmaybe-uninitialized (like -Wall, -Wextra or -Wuninitia= lized). > > >=20 > > > -O0 and/or no ASan, and the offending code compiles cleanly without a= ny > > > warnings. Somehow, the combination of enabling ASan and optimization > > > (anything > -O0, but not -Os) triggers it again, it seems? > > >=20 > > > I can observe this with the testcase attached here in this bug report. > >=20 > > -fsanitize=3Daddress is likely to derail optimization enough to make su= ch > > occurences more likely, I think we have plenty of duplicate bugreports > > for this. >=20 > So it seems this is still hapening with -O1 -fsanitize=3Daddress (occurri= ng > for me too with GCC 13.1.0), yet this specific bug is marked as "fixed" a= nd > there's a mention of duplicate bugreports (I can see one unconfirmed > pointed-to by this issue). Is opening of another bug, focusing on -O1 > -fsanitize=3Daddress, going to help get this fixed? I can confirm this is still valid. Build with flags '-O1 -fsanitize=3Daddress -Wall -Werror' is still failing. Tested for version 12.1, 12.2, 12.3, 13.1, 13.2 Shouldn't it be reopen? If there is some other ticket related to it, could someone link it here?=