From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B93393858C33; Wed, 3 May 2023 20:39:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B93393858C33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683146345; bh=uGC19srZFBuWL5H7ZOXGTdrTiNs1A+V4Yj89qd9PXFM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=boJon1ar6cP7vs1MDjyhrdz3NOlTby27URZYFyLo6QaxBtj8ncWF9WMCORsxMZQof dgt/aBgj+iuEjhp3XaDojcaa5Srbt3O9DXdwZABhF2lsEpV1mwVki01wQlzwgv1zp1 d96hfA4qo20ZJmcwxMg/7KPWOgdnrrpwcs6+4lyI= From: "pinskia at gcc dot 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:39:05 +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: 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=3D109719 --- Comment #8 from Andrew Pinski --- (In reply to Christian Hergert from comment #6) > (In reply to Andrew Pinski from comment #2) > > HUH? omit frame pointer is on by default on x86_64. >=20 > Yes, Fedora 38 changed the default compiler flags to > `-fno-omit-frame-pointer` so that the system can be profiled more reliabl= y. So you should report this to Fedora's team. >=20 > > What target is this on? >=20 > x86_64 >=20 > > What exact command line is being used to compile the sources? If this on > > x86_64, you might still need -mno-omit-leaf-frame-pointer too. >=20 > No doubt, I have `-mno-omit-leaf-frame-pointer` too. I am suspecting the issue is inside the linux kernel ... Anyways we need much more information here. A sample simple program which shows that GCC is doing the wrong thing. Maybe it is the linux frame pointer walker going wrong.=