public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112468] [14 Regression] Missed phi-opt after recent change
Date: Fri, 10 Nov 2023 07:25:08 +0000 [thread overview]
Message-ID: <bug-112468-4-GYsp2yLCzm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112468-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112468
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnfchris at gcc dot gnu.org
--- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hmm I rather think PHI ops should handle that null like other passes do. The
folding is supposed to already test and only happen if it succeeds.
This prevents match.pd from having to have a second check on every IFN usage.
next prev parent reply other threads:[~2023-11-10 7:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 19:55 [Bug tree-optimization/112468] New: " law at gcc dot gnu.org
2023-11-09 20:05 ` [Bug tree-optimization/112468] " pinskia at gcc dot gnu.org
2023-11-10 3:55 ` pinskia at gcc dot gnu.org
2023-11-10 4:06 ` pinskia at gcc dot gnu.org
2023-11-10 7:25 ` tnfchris at gcc dot gnu.org [this message]
2023-11-10 7:52 ` pinskia at gcc dot gnu.org
2023-11-10 8:31 ` rguenth at gcc dot gnu.org
2023-11-13 1:22 ` hp at gcc dot gnu.org
2023-11-13 7:04 ` tnfchris at gcc dot gnu.org
2023-12-10 19:34 ` pinskia at gcc dot gnu.org
2023-12-13 15:41 ` [Bug tree-optimization/112468] [14 Regression] Missed phi-opt after recent change (phi-opt-24.c) hp at gcc dot gnu.org
2023-12-13 15:44 ` tnfchris at gcc dot gnu.org
2023-12-14 0:36 ` hp at gcc dot gnu.org
2023-12-19 2:40 ` sandra at gcc dot gnu.org
2024-01-10 17:19 ` cvs-commit at gcc dot gnu.org
2024-01-10 17:21 ` tnfchris 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-112468-4-GYsp2yLCzm@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).