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 0F19B3858D33; Wed,  3 May 2023 20:38:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F19B3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683146297;
	bh=wHX8SLQ0VL4jlVsxSS6rIyJrec21YSvZOTRTqY3dsfE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vC0Tg8WkrCdBlK07sEa93f+jDUMRx14FHROz/0kdeMzhG+f7UXsVJhEu6404fHPlO
	 X7VDjSrWFiJN9bUwA1/8QZMu7zqnRbVChp5aevW6vEhpn/pe1ki87POZZ3U9kflpQu
	 /z+BfauwW7KK8MCftyqH8sYW22RaeNiVhZxSNaSM=
From: "chergert at redhat dot com" <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:38:16 +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: chergert at redhat dot com
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-IUMSfd17GD@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 #7 from Christian Hergert <chergert at redhat dot com> ---
(In reply to Andrew Pinski from comment #3)
> 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?

Because the stack unwinding comes from the Linux kernel, which the default
unwinder can only support frame-pointers. The DWARF unwinder was removed lo=
ng
ago.

Additionally, it can't use `.eh_frame_hdr` either.=