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 EC4573858D39; Tue,  9 Apr 2024 19:48:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC4573858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712692108;
	bh=EjNhNV3/tgW/Qn2/KAckI5cGD7uXGSDTwmWfZ82FHwM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=GLi0SsDSn6yjmSI3mmOb9Rt0Ihf1DtnxbojBb764efuzOxdKyJa9BW6JJSbI+zuOb
	 IrBLErsZaQx89mqq7g2JQJv7SUouwtI5g3aFgNzmiMI2ghTgvMfCdstcVBxJT5tRco
	 nYbT7J7xCNZ3Bys6Spq+F2w6guLUh4xn7Ny/YnlY=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114664] -fno-omit-frame-pointer causes an ICE
 during the build of the greenlet package
Date: Tue, 09 Apr 2024 19:48:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-114664-4-tKcbllk7rH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114664-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=3D114664

--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> Pre-IRA fix was done to specifically reject this:
> https://inbox.sourceware.org/gcc-patches/
> ab3a61990702021658w4dc049cap53de8010a7d8626e@mail.gmail.com/

Then that would seem to indicate that mentioning the frame pointer reg in t=
he
asm clobber list is an error, but how are users supposed to know whether
-fno-omit-frame-pointer is in effect or not?  I've looked and there is no
pre-defined macro a user could check.=