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 1EC6F3858D20; Tue, 11 Jul 2023 19:50:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1EC6F3858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689105027;
	bh=Jj5BCGDX3mHzP9FYwhEGqNbd3lrx1oh6HfAk0c5aDj8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=cSOY/dtmmT1J5LRpCNTD+rP61ENrxgrBwmVIck+VbpdlguTfiz2mkp7RBKrU7+iE9
	 eFlGJ+2m/3cZQ3ml5UunDAvKs5bwPl/zOstlwCU2+6OF9frqsjOQGN8dfOUjkNwO0h
	 bYi1zHUbMHRuM99fgQNfZd4oA2v5A8RCv/IJnbxg=
From: "bjorn at kernel dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110634] Incorrect RISC-V assembly with
 -fno-omit-frame-pointer
Date: Tue, 11 Jul 2023 19:50:26 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bjorn at kernel dot org
X-Bugzilla-Status: WAITING
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-110634-4-q9payDdIxy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110634-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110634-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=3D110634

--- Comment #2 from Bj=C3=B6rn T=C3=B6pel <bjorn at kernel dot org> ---
(In reply to Andrew Pinski from comment #1)
> I don't see where in any of the spec mentioned that storing of ra is need=
ed
> at all. That is it does not read ambigous to me at all. It just mentions =
for
> a frame pointer, the frame pointer needs to be saved and nothing about ra.
>=20
> This is totally different from the power ABI.

Hmm, but is a frame-pointer w/o the ability to unwind useful? Or am I missi=
ng
something?=