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/110173] [14 Regression] Missed Dead Code Elimination when using __builtin_unreachable since r14-569-g21e2ef2dc25
Date: Thu, 08 Jun 2023 18:26:49 +0000 [thread overview]
Message-ID: <bug-110173-4-vHP6NCThm5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110173-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110173
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Hmm
> static void i() { *h = j(); }
> static int *j(unsigned o) {
>
> I suspect this is just might be another one of these cases where a variable
> is uninitialized gets a different value now.
Yes it is definitely related to that variable being uninitialized.
if you replace o with either 1 or 0, the call to foo is there even in GCC 13.
I think this can be marked as a non-regression.
next prev parent reply other threads:[~2023-06-08 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 14:07 [Bug tree-optimization/110173] New: " theodort at inf dot ethz.ch
2023-06-08 14:09 ` [Bug tree-optimization/110173] " theodort at inf dot ethz.ch
2023-06-08 14:17 ` pinskia at gcc dot gnu.org
2023-06-08 18:26 ` pinskia at gcc dot gnu.org [this message]
2023-06-08 18:41 ` pinskia at gcc dot gnu.org
2023-06-08 18:43 ` [Bug tree-optimization/110173] " pinskia at gcc dot gnu.org
2023-06-08 18:46 ` [Bug tree-optimization/110173] [13/14 Regression] Missed Dead Code Elimination when using __builtin_unreachable pinskia at gcc dot gnu.org
2023-06-19 12:05 ` theodort at inf dot ethz.ch
2023-07-27 9:26 ` rguenth at gcc dot gnu.org
2024-03-08 15:35 ` law at gcc dot gnu.org
2024-05-21 9:15 ` [Bug tree-optimization/110173] [13/14/15 " 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-110173-4-vHP6NCThm5@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).