public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/99151] Missed optimization: Superfluous stack frame and code with noreturn or __builtin_unreachable()
Date: Mon, 01 Mar 2021 13:21:35 +0000 [thread overview]
Message-ID: <bug-99151-4-5AoZGVcSrc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99151-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99151
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We certainly don't claim it is the exact same thing as using the noreturn
attribute, it is not.
We could in profile.c ignore edges that lead to basic blocks that start with
__builtin_unreachable () call as the first non-debug stmt after labels if it
was really important, but I'm not convinced it is.
prev parent reply other threads:[~2021-03-01 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 14:45 [Bug c/99151] New: " sebastian.huber@embedded-brains.de
2021-02-18 14:52 ` [Bug c/99151] " jakub at gcc dot gnu.org
2021-02-18 14:56 ` sebastian.huber@embedded-brains.de
2021-02-18 19:15 ` pinskia at gcc dot gnu.org
2021-02-19 6:46 ` [Bug middle-end/99151] " sebastian.huber@embedded-brains.de
2021-03-01 11:17 ` ebotcazou at gcc dot gnu.org
2021-03-01 12:36 ` sebastian.huber@embedded-brains.de
2021-03-01 12:53 ` ebotcazou at gcc dot gnu.org
2021-03-01 13:04 ` sebastian.huber@embedded-brains.de
2021-03-01 13:21 ` jakub at gcc dot gnu.org [this message]
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-99151-4-5AoZGVcSrc@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).