public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified
Date: Wed, 23 Aug 2023 20:57:31 +0000	[thread overview]
Message-ID: <bug-111096-4-qUDngzSTYE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111096-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #5)
> This was a deliberate design choice.  Although the frame chain is not set up
> by code that omits the frame pointer, the chain of frames that are set up by
> other functions is still valid this way.  This ensures that any code that
> does try to walk the frame chain will not crash.  If we reused the frame
> pointer for other purposes, then any code trying to walk the frame chain (eg
> backtrace()) would encounter an invalid record and likely crash.


Would it make sense to document this somewhere?  Or did I just miss it? :-)

  parent reply	other threads:[~2023-08-23 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  5:25 [Bug rtl-optimization/111096] New: " tkoenig at gcc dot gnu.org
2023-08-22  5:48 ` [Bug target/111096] " pinskia at gcc dot gnu.org
2023-08-22  5:52 ` pinskia at gcc dot gnu.org
2023-08-22  9:18 ` tkoenig at gcc dot gnu.org
2023-08-22 16:49 ` gccbug at provalid dot com
2023-08-23 10:51 ` rearnsha at gcc dot gnu.org
2023-08-23 15:31 ` rearnsha at gcc dot gnu.org
2023-08-23 20:57 ` tkoenig at gcc dot gnu.org [this message]
2023-08-24 14:29 ` rearnsha at gcc dot gnu.org
2023-08-25 18:15 ` tkoenig at gcc dot gnu.org

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-111096-4-qUDngzSTYE@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).