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 96A9E3858D28; Wed,  3 May 2023 20:29:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 96A9E3858D28
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683145752;
	bh=eoYK30lOxMIyMl64DVtcatrgweJA0o4iRijeu/VipD0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kVR9CyglwL34oNkdAqqPuoA4Hgf9f0s7VBfEAT849mbdUOJbjrUBSfvmynGX+0wSE
	 k2Qtze1cGctloieANmAp9VDcoidPNAjNNOUmEkKiP1RQrmHb19NJ8ewzmuBHh0NY+c
	 h25AG9EBTUfeRZa7xDSNWAg0qmNUhMKzS1tPsRok=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109719] Truncated frame-pointer unwinding via Linux perf
 with g++
Date: Wed, 03 May 2023 20:29:12 +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: 13.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: <bug-109719-4-rQV2vDvr4s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109719-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109719-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=3D109719

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Also on x86_64, frame pointers are not required by the ABI so this is not an
ABI issue. Why instead are you not using the dwarf2 unwind tables that are
generated by default too?=