public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114682] const_array[i].b where i is PHI<0,1,2> is not folded
Date: Thu, 11 Apr 2024 06:38:26 +0000	[thread overview]
Message-ID: <bug-114682-4-I5QLWxWSz0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114682-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114682

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-04-11

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note it isn't necessarily always an improvement.  It's also not really PRE
but FRE when you do PHI translation.  There's an argument that we should
try PHI translation in FRE to at least catch cases like this where
the replacement is simply

  # i_3 = PHI <2(4), 0(2), 1(3)>
  _12 = (int) i_3;

Note there's also that "frankenstein" phiprop pass which does remotely
similar things.

      parent reply	other threads:[~2024-04-11  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 19:31 [Bug tree-optimization/114682] New: " pinskia at gcc dot gnu.org
2024-04-10 19:32 ` [Bug tree-optimization/114682] " pinskia at gcc dot gnu.org
2024-04-11  6:38 ` rguenth 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-114682-4-I5QLWxWSz0@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).