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/66002] paq8p benchmark 50% slower than clang on sandybridge
Date: Mon, 04 May 2015 14:06:00 -0000	[thread overview]
Message-ID: <bug-66002-4-17c66dKkWS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66002-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
VRP performs jump-threading to else-if style but phiopt doesn't handle the
min-max case with split PHIs

  if (wt_25 < -32768)
    goto <bb 5>;
  else
    goto <bb 4>;

  <bb 4>:
  if (wt_25 > 32767)
    goto <bb 6>;
  else
    goto <bb 5>;

  <bb 5>:
  # wt_31 = PHI <wt_25(4), -32768(3)>

  <bb 6>:
  # wt_3 = PHI <wt_31(5), 32767(4)>
  _26 = (short int) wt_3;

vs.

  if (wt_24 < -32768)
    goto <bb 6>;
  else
    goto <bb 4>;

  <bb 4>:
  if (wt_24 > 32767)
    goto <bb 6>;
  else
    goto <bb 5>;

  <bb 5>:

  <bb 6>:
  # wt_2 = PHI <-32768(3), wt_24(5), 32767(4)>
  _25 = (short int) wt_2;

so it looks like phiopt "depends" on mergephi (I always wondered what pass
that is useful for...).  Currently that pass runs right before VRP which
definitely does _not_ depend on it.  I'd move it right before ifcombine
which is the first pass that might care.


  parent reply	other threads:[~2015-05-04 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  7:20 [Bug tree-optimization/66002] New: " trippels at gcc dot gnu.org
2015-05-04 12:47 ` [Bug tree-optimization/66002] " rguenth at gcc dot gnu.org
2015-05-04 12:55 ` trippels at gcc dot gnu.org
2015-05-04 13:43 ` rguenth at gcc dot gnu.org
2015-05-04 13:57 ` rguenth at gcc dot gnu.org
2015-05-04 14:06 ` rguenth at gcc dot gnu.org [this message]
2015-05-04 14:11 ` trippels at gcc dot gnu.org
2015-05-06 11:51 ` rguenth at gcc dot gnu.org
2015-05-06 12:13 ` rguenth at gcc dot gnu.org
2015-05-07  9:53 ` rguenth at gcc dot gnu.org
2015-05-07  9:54 ` rguenth 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-66002-4-17c66dKkWS@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).