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 tree-optimization/111799] [14 Regression] Missed Dead Code Elimination since r14-2365-g2e406f0753e Date: Mon, 16 Oct 2023 04:08:25 +0000 [thread overview] Message-ID: <bug-111799-4-cLcp9ihnm4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111799-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111799 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Hmm, I think we reach __builtin_unreachable always and that is confusing everything. If we inline s early on (via using the always_inline attribute). main turns into just __builtin_unreachable .
next prev parent reply other threads:[~2023-10-16 4:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-13 15:46 [Bug tree-optimization/111799] New: " theodort at inf dot ethz.ch 2023-10-13 15:48 ` [Bug tree-optimization/111799] " pinskia at gcc dot gnu.org 2023-10-13 15:50 ` pinskia at gcc dot gnu.org 2023-10-13 15:52 ` pinskia at gcc dot gnu.org 2023-10-16 4:08 ` pinskia at gcc dot gnu.org [this message] 2023-10-17 11:08 ` theodort at inf dot ethz.ch 2023-10-18 23:55 ` [Bug middle-end/111799] " pinskia at gcc dot gnu.org 2024-03-07 21:04 ` law at gcc dot gnu.org 2024-03-09 5:43 ` law at gcc dot gnu.org 2024-05-07 7:42 ` [Bug middle-end/111799] [14/15 " rguenth 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-111799-4-cLcp9ihnm4@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).