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 E77A33860012; Wed, 14 Feb 2024 18:13:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E77A33860012
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707934383;
	bh=ZtSsdi0+g5yzUYHtN1X8myTCCLJcvWet/PD8VVByXUs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=uKfuBhXkKVUqh53DLCSq9Itp0UpQhGs35BIp7eGVV2ZsJoKmMBH43gzYFdHgo4ZfQ
	 in0zAkhRxFvq9sOsnrceliA+C2gnOLnoN46JiLV6/obLWbk5KxYyAll7Gu0p5ks72G
	 e0hgSUYpFMsp7EPU9OurEgt0H/CAyphiZkWl/lMo=
From: "torvalds@linux-foundation.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113921] Output register of an "asm volatile goto" is
 incorrectly clobbered/discarded
Date: Wed, 14 Feb 2024 18:13:02 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 11.4.0
X-Bugzilla-Keywords: inline-asm
X-Bugzilla-Severity: normal
X-Bugzilla-Who: torvalds@linux-foundation.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: <bug-113921-4-hDwQO1GoHY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113921-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113921-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #2 from Linus Torvalds <torvalds@linux-foundation.org> ---
(In reply to Jakub Jelinek from comment #1)
> Bisection points to r12-5301-g045206450386bcd774db3bde0c696828402361c6
> making the problem go away,

Well, that certainly explains why I can't see the problem with my gcc 13.2.=
1.

It looks like that commit is in gcc-12.1.o and later:

   git log --oneline --all --grep=3D"tree-optimization/102880 - improve CD-=
DCE"

only returns that one commit, and=20

   git name-rev --refs '*releases*' 045206450386b

says "gcc-12.1.0~3038".

So we could make our workaround option be something like

   config GCC_ASM_GOTO_WORKAROUND
     def_bool y
     depends on CC_IS_GCC && GCC_VERSION < 120100

but maybe there is some backporting policy with gcc that my quick git check
missed?=