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/55862] [4.8 Regression] ICE in compute_antic, at tree-ssa-pre.c:2495
Date: Mon, 07 Jan 2013 13:50:00 -0000	[thread overview]
Message-ID: <bug-55862-4-RFBs88UYOs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55862-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55862

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-07 13:50:03 UTC ---
Followup, because of PR55888.  We have

  <bb 11>:
  # c_21 = PHI <p_66(18), p_67(3)>
  # p_41 = PHI <p_66(18), p_67(3)>
  a.1_42 = a;
  goto <bb 5>;

  <bb 5>:
  # c_57 = PHI <c_1(16), c_21(11)>
  # a.1_63 = PHI <a.1_25(16), a.1_42(11)>
  # p_65 = PHI <p_30(16), p_41(11)>
  *c_57 = 0;

and when PHI-translating p_65 we end up with p_41 (or c_21 value-ized).  But
AVAIL_OUT of BB 11 is:

debug[0] := { c_12(D) (0014), p_32(D) (0027), g.0_11 (0013), c_21 (0033),
a.1_42 (0034) }

thus contains _only_ c_21 (well, exactly one expression per value - it is
a value set after all).  And clean via valid_in_sets does

    case NAME:
      return bitmap_set_contains_expr (AVAIL_OUT (block), expr);

thus checks for the expression availability.  That looks bogus to me.
Instead we should verify if there is a leader for the NAME in AVAIL_OUT.


  parent reply	other threads:[~2013-01-07 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 14:13 [Bug tree-optimization/55862] New: " antoine.balestrat at gmail dot com
2013-01-03 16:20 ` [Bug tree-optimization/55862] [4.8 Regression] " rguenth at gcc dot gnu.org
2013-01-04 11:59 ` rguenth at gcc dot gnu.org
2013-01-04 13:29 ` rguenth at gcc dot gnu.org
2013-01-04 13:29 ` rguenth at gcc dot gnu.org
2013-01-07 13:50 ` rguenth at gcc dot gnu.org [this message]
2013-01-07 14:06 ` 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-55862-4-RFBs88UYOs@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).