From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8EED3858422; Mon, 29 May 2023 01:27:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8EED3858422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685323674; bh=xvbI3WulKzbXtb89jzkt0oLPf1p7O1/dt2bIzaqnmRk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Q+S/3K3BTrpnN2JgsGvx/kjLhId7421+kMw3Gw6ytWJxdD7xineC+jQrr/yhRGGex jurxLEayafIPzhswJGmXf236zVnrxNGj3vvJ9TbW2b030srr2UDLDca8jRzEia9tW5 fv3fZIOxYzde5xZnCksZodKR4wf80IA4I+aXorP0= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110016] Possible miscodegen when inlining std::condition_variable::wait predicate causes deadlock Date: Mon, 29 May 2023 01:27:54 +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.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: 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=3D110016 --- Comment #7 from Andrew Pinski --- I can reproduce the failure on aarch64-linux-gnu on the trunk with `-std=3D= c++17 -pthread -O2 -fsanitize=3Dthread -fno-inline` so your theory about inlining= is causing an issue is so incorrect.=