public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100811] Consider not omitting frame pointers by default on targets with many registers
Date: Thu, 25 May 2023 16:40:17 +0000 [thread overview]
Message-ID: <bug-100811-4-uU9w771uxl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100811-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #7 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> I think aarch64 defaults to -fno-omit-frame-pointer anyway.
> /* Disable fomit-frame-pointer by default. */
> { OPT_LEVELS_ALL, OPT_fomit_frame_pointer, NULL, 0 },
It's required by some (all?) AArch64 ABIs, certainly on GNU/Linux.
next prev parent reply other threads:[~2023-05-25 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 11:34 [Bug target/100811] New: " grasland at lal dot in2p3.fr
2021-05-28 11:40 ` [Bug target/100811] " jakub at gcc dot gnu.org
2021-05-28 11:46 ` fw at gcc dot gnu.org
2021-05-28 14:06 ` pinskia at gcc dot gnu.org
2023-05-25 16:06 ` hiraditya at msn dot com
2023-05-25 16:30 ` pinskia at gcc dot gnu.org
2023-05-25 16:35 ` jakub at gcc dot gnu.org
2023-05-25 16:40 ` fw at gcc dot gnu.org [this message]
2023-05-25 17:16 ` hiraditya at msn dot com
2023-05-25 17:19 ` jakub at gcc dot gnu.org
2023-05-26 13:37 ` xry111 at gcc dot gnu.org
2023-05-26 13:47 ` jakub 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-100811-4-uU9w771uxl@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).