public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/48144] ICE: in code_motion_path_driver, at sel-sched.c:6575 with -fselective-scheduling2 and custom flags
Date: Tue, 22 Mar 2011 16:29:00 -0000	[thread overview]
Message-ID: <bug-48144-4-lgLk6BLeJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48144-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrey Belevantsev <abel at gcc dot gnu.org> 2011-03-22 15:58:52 UTC ---
Created attachment 23751
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23751
Current patch

The ICE turned out to be the new one.  We are updating the data sets on the
bookkeeping blocks for the reasons outlined in the long comment in sel-sched.c.
 When doing this, we not only remove some insns but also add previous unknown
insns (possibly transformed) to the av set of the bookkeeping block.  The same
insns might also happen to be in the upper av sets, but their transformation
history is not reflecting the mentioned updates.  We were missing this case
when we have fixed the problem only for bookkeeping insns.  

Fixed by simply always picking up the transformation history from the blocks we
are processing on the way down.  This patch may let us get rid of the earlier
originators stuff introduced to solve this for bookkeeping insns.

Zdenek, does this patch work for you?


  parent reply	other threads:[~2011-03-22 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  2:53 [Bug rtl-optimization/48144] New: " zsojka at seznam dot cz
2011-03-16  8:36 ` [Bug rtl-optimization/48144] " abel at gcc dot gnu.org
2011-03-20 18:53 ` zsojka at seznam dot cz
2011-03-22 16:29 ` abel at gcc dot gnu.org [this message]
2011-03-22 20:19 ` zsojka at seznam dot cz
2011-03-26 12:35 ` abel at gcc dot gnu.org
2011-04-07  7:05 ` abel at gcc dot gnu.org
2011-04-07 12:07 ` abel at gcc dot gnu.org
2011-04-07 12:07 ` abel 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-48144-4-lgLk6BLeJ5@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).