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: Fri, 28 May 2021 11:46:14 +0000 [thread overview] Message-ID: <bug-100811-4-eMKQ7LEvcD@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 Florian Weimer <fw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at gcc dot gnu.org --- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> --- I expect that profilers will soon be able to use the shadow stack on x86, which will be more efficient and reliable than traversing frame pointers.
next prev parent reply other threads:[~2021-05-28 11:46 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 [this message] 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 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-eMKQ7LEvcD@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: linkBe 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).