public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/52113] [4.7 regression][lower-subreg.c] ICE: in extract_insn, at recog.c:2123
Date: Sat, 04 Feb 2012 00:10:00 -0000 [thread overview]
Message-ID: <bug-52113-4-06wpfz7gPK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52113-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52113
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-04 00:10:04 UTC ---
Created attachment 26568
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26568
gcc47-pr52113.patch
Untested fix. The problem is that lower-subreg relies on recog_memoized being
performed on all insns before changing decomposable regs into concatn, because
otherwise they might not be recognized. They will be fixed up during the pass
later on, but if they weren't recognized first, extract_insn will already ICE.
Don't have time to test this for avr, will only include it in my next
x86_64/i686 bootstrap/regtest.
next prev parent reply other threads:[~2012-02-04 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 17:35 [Bug target/52113] New: [4.7 regression][avr] " mhlavink at redhat dot com
2012-02-03 18:47 ` [Bug rtl-optimization/52113] [4.7 regression][lower-subreg.c] " gjl at gcc dot gnu.org
2012-02-04 0:10 ` jakub at gcc dot gnu.org [this message]
2012-02-04 1:15 ` gjl at gcc dot gnu.org
2012-02-04 7:39 ` jakub at gcc dot gnu.org
2012-02-04 12:48 ` jakub at gcc dot gnu.org
2012-02-04 12:59 ` jakub 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-52113-4-06wpfz7gPK@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).