public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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:39:05 +0000	[thread overview]
Message-ID: <bug-109719-4-mcVCz2IiEJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109719-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109719

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(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.
> 
> Yes, Fedora 38 changed the default compiler flags to
> `-fno-omit-frame-pointer` so that the system can be profiled more reliably.

So you should report this to Fedora's team.

> 
> > What target is this on?
> 
> x86_64
> 
> > 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.
> 
> 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.

  parent reply	other threads:[~2023-05-03 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 20:21 [Bug c++/109719] New: " chergert at redhat dot com
2023-05-03 20:23 ` [Bug c++/109719] " chergert at redhat dot com
2023-05-03 20:28 ` [Bug target/109719] " pinskia at gcc dot gnu.org
2023-05-03 20:29 ` pinskia at gcc dot gnu.org
2023-05-03 20:31 ` chergert at redhat dot com
2023-05-03 20:33 ` chergert at redhat dot com
2023-05-03 20:36 ` chergert at redhat dot com
2023-05-03 20:38 ` chergert at redhat dot com
2023-05-03 20:39 ` pinskia at gcc dot gnu.org [this message]
2023-05-03 20:43 ` chergert at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109719-4-mcVCz2IiEJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).