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 middle-end/66375] [4.8/4.9/5 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu
Date: Tue, 02 Jun 2015 09:31:00 -0000	[thread overview]
Message-ID: <bug-66375-4-1TaXfOdIVA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66375-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
PRE doesn't seem to do sth wrong here.  The testcase can be fixed by for
example disabling VRP2.  VRP2 needs either store-motion or complete unrolling
to
make it trigger the miscompile.  Nicest IL before VRP2 is with -fno-ivopts
-fno-tree-loop-im.  The transform VRP2 does is

Folding statement: if (a.4_17 <= 13)
Simplified relational if (a.4_17 <= 13)
 into if (a.4_17 != 14)

and

  Registering jump thread: (6, 7) incoming edge;  (7, 8) normal;
  Threaded jump 6 --> 7 to 12

  <bb 6>:
  # prephitmp_3 = PHI <prephitmp_22(5)>
  # prephitmp_39 = PHI <prephitmp_22(5)>

  <bb 7>:
  # prephitmp_26 = PHI <prephitmp_39(6), pretmp_23(3)>
  if (prephitmp_26 != 113)
    goto <bb 8>;
  else
    goto <bb 9>;

  <bb 8>:
  __builtin_abort ();

so it looks jump-threading related to me.  Somehow the equivalences I
see being recorded miss the backedge for prephitmp_22 but only record zero.


  parent reply	other threads:[~2015-06-02  9:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02  5:43 [Bug tree-optimization/66375] New: " su at cs dot ucdavis.edu
2015-06-02  5:49 ` [Bug middle-end/66375] " pinskia at gcc dot gnu.org
2015-06-02  6:16 ` [Bug middle-end/66375] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org
2015-06-02  8:50 ` rguenth at gcc dot gnu.org
2015-06-02  9:31 ` rguenth at gcc dot gnu.org [this message]
2015-06-02 10:31 ` rguenth at gcc dot gnu.org
2015-06-02 11:21 ` rguenth at gcc dot gnu.org
2015-06-02 11:56 ` rguenth at gcc dot gnu.org
2015-06-02 14:34 ` rguenth at gcc dot gnu.org
2015-06-03  7:57 ` [Bug middle-end/66375] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-09 23:55 ` bernhard.kaindl at thalesgroup dot com
2015-06-10  7:01 ` [Bug middle-end/66375] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2015-06-18 14:04 ` rguenth at gcc dot gnu.org
2015-06-23  8:28 ` [Bug middle-end/66375] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-06-26 20:04 ` [Bug middle-end/66375] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:32 ` jakub at gcc dot gnu.org
2022-10-25 11:40 ` cvs-commit 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-66375-4-1TaXfOdIVA@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).