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/64700] Sink common code through PHI
Date: Tue, 20 Jul 2021 02:52:16 +0000	[thread overview]
Message-ID: <bug-64700-4-yyiDYeSBoC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64700-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org
                 CC|                            |pinskia at gcc dot gnu.org
           Severity|normal                      |enhancement

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
  <bb 7> [local count: 958878293]:
  if (dir_lsm.26_39 == 1)
    goto <bb 8>; [34.00%]
  else
    goto <bb 9>; [66.00%]

  <bb 8> [local count: 326018623]:
  _11 = arr1.6_10 + _5;
  _12 = *_11;
  goto <bb 10>; [100.00%]

  <bb 9> [local count: 632859670]:
  _14 = arr2.9_13 + _5;
  _15 = *_14;

  <bb 10> [local count: 958878293]:
  # cstore_45 = PHI <_12(8), _15(9)>

PHI-OPT improvements that I am working on might be able to handle this case
too.
MEM_EXPR is a little harder than the normal expression as you need to check the
access type for aliasing reasons.

Note PHI-OPT does handle the casting case already (but it is not listed here).

  parent reply	other threads:[~2021-07-20  2:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 22:01 [Bug tree-optimization/64700] New: " law at redhat dot com
2015-01-21  9:43 ` [Bug tree-optimization/64700] " rguenth at gcc dot gnu.org
2015-01-21 20:42 ` law at redhat dot com
2021-07-20  2:52 ` pinskia at gcc dot gnu.org [this message]
2023-05-08  7:38 ` cvs-commit at gcc dot gnu.org
2023-05-08  7:40 ` pinskia at gcc dot gnu.org
2023-05-15  0:27 ` pinskia 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-64700-4-yyiDYeSBoC@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).