From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B0C893858D33; Tue, 11 Jul 2023 19:52:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B0C893858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689105127; bh=Af8atHM4TpNLPDjWPSpxquR7c0nP3wg8/ePS7cV7P9U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lstVnPIOuNL6Cry63wnqMOyhhCsocYZxOBH2XxUJDgyciaz1XBDq4BnhgAcztGmkQ kg+2vwhuuUV0PXV7Jl05riVBHTGf79t+xbMnUy2arNSTO7fgVCOhiKuRWjlZmX3USq Eo8l21EidK5pSlgmjYmoanJybpCtPI5IjYDlNEhc= From: "pinskia at gcc dot 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:52:07 +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: pinskia at gcc dot gnu.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: 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=3D110634 --- Comment #3 from Andrew Pinski --- (In reply to Bj=C3=B6rn T=C3=B6pel from comment #2) > Hmm, but is a frame-pointer w/o the ability to unwind useful? Or am I > missing something? You know what, you are better ask the ABI folks because GCC follows the ABI specifically.=