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/109943] [13/14 Regression] Missed Dead Code Elimination when using __builtin_unreachable since r13-6834-g41ade3399bd
Date: Mon, 21 Aug 2023 23:09:56 +0000 [thread overview]
Message-ID: <bug-109943-4-1WeaVPb2QJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109943-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109943
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2023-08-21
Status|UNCONFIRMED |NEW
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
For the testcase in comment #0, fre3 is able to optmize it away (in GCC
12.3.0):
Applying pattern match.pd:636, gimple-match.cc:47124
Match-and-simplified _10 % _8 to 0
That is because we figure out that _10 is the same as _8 somehow.
Confirmed.
next prev parent reply other threads:[~2023-08-21 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 13:30 [Bug tree-optimization/109943] New: " theodort at inf dot ethz.ch
2023-05-23 15:56 ` [Bug tree-optimization/109943] " rguenth at gcc dot gnu.org
2023-06-20 16:34 ` theodort at inf dot ethz.ch
2023-07-27 9:26 ` rguenth at gcc dot gnu.org
2023-08-21 23:09 ` pinskia at gcc dot gnu.org [this message]
2024-01-12 13:50 ` rguenth at gcc dot gnu.org
2024-01-12 13:52 ` rguenth at gcc dot gnu.org
2024-05-21 9:15 ` [Bug tree-optimization/109943] [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-109943-4-1WeaVPb2QJ@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).