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/53701] ICE on ia64 (when building Allegro 4.4) in sel-sched
Date: Wed, 08 Aug 2012 11:26:00 -0000	[thread overview]
Message-ID: <bug-53701-4-4EBUckc7av@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53701-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Andrey Belevantsev <abel at gcc dot gnu.org> 2012-08-08 11:26:01 UTC ---
Created attachment 27959
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27959
proposed patch

The problem is that when checking expressions that are blocked for movement
because of recently created bookkeeping code we need to consider also all old
forms of those expressions as they could get transformed on the way up. 
PR53975 just uncovers this bug but is actually unrelated.

The attached patch fixes the testcase but is not yet otherwise tested.


  parent reply	other threads:[~2012-08-08 11:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 23:54 [Bug c/53701] New: ICE on ia64 (when building Allegro 4.4) tobias.han at gmx dot de
2012-06-16 23:58 ` [Bug rtl-optimization/53701] " pinskia at gcc dot gnu.org
2012-06-17  9:47 ` [Bug rtl-optimization/53701] ICE on ia64 (when building Allegro 4.4) in sel-sched kibi at debian dot org
2012-06-17 10:36 ` mikpe at it dot uu.se
2012-06-17 14:34 ` mikpe at it dot uu.se
2012-07-27  7:14 ` mikpe at it dot uu.se
2012-08-06 14:22 ` abel at gcc dot gnu.org
2012-08-08 11:26 ` abel at gcc dot gnu.org [this message]
2012-08-09 14:08 ` abel at gcc dot gnu.org
2012-10-16 13:22 ` abel at gcc dot gnu.org
2012-10-22 19:35 ` abel at gcc dot gnu.org
2012-10-22 19:40 ` 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-53701-4-4EBUckc7av@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).