public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55204] New: [4.8 Regression] ICE: in extract_insn, at recog.c:2140 (unrecognizable insn) with -O --param loop-invariant-max-bbs-in-loop=0 Date: Sun, 04 Nov 2012 12:14:00 -0000 [thread overview] Message-ID: <bug-55204-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55204 Bug #: 55204 Summary: [4.8 Regression] ICE: in extract_insn, at recog.c:2140 (unrecognizable insn) with -O --param loop-invariant-max-bbs-in-loop=0 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 28610 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28610 reduced testcase Compiler output: $ gcc -O --param loop-invariant-max-bbs-in-loop=0 testcase.ctestcase.c: In function 'f1': testcase.c:18:1: error: unrecognizable insn: } ^ (insn 53 50 24 5 (set (reg:SI 5 di [77]) (plus:SI (subreg:SI (reg:HI 7 sp) 0) (const_int -248 [0xffffffffffffff08]))) testcase.c:13 -1 (nil)) testcase.c:18:1: internal compiler error: in extract_insn, at recog.c:2140 0x9969ea _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /mnt/svn/gcc-trunk/gcc/rtl-error.c:110 0x996a7a _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /mnt/svn/gcc-trunk/gcc/rtl-error.c:118 0x9524d8 extract_insn(rtx_def*) /mnt/svn/gcc-trunk/gcc/recog.c:2140 0x9526eb extract_insn_cached(rtx_def*) /mnt/svn/gcc-trunk/gcc/recog.c:2043 0x79f91d cleanup_subreg_operands(rtx_def*) /mnt/svn/gcc-trunk/gcc/final.c:2968 0x94dc60 split_insn /mnt/svn/gcc-trunk/gcc/recog.c:2857 0x956401 split_all_insns() /mnt/svn/gcc-trunk/gcc/recog.c:2911 0x956558 rest_of_handle_split_after_reload /mnt/svn/gcc-trunk/gcc/recog.c:3795 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r193125 - crash r192654 - OK r191586 - OK 4.7 r191640 - OK
next reply other threads:[~2012-11-04 12:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-04 12:14 zsojka at seznam dot cz [this message] 2012-11-04 13:18 ` [Bug rtl-optimization/55204] " mpolacek at gcc dot gnu.org 2012-11-04 20:07 ` rsandifo at gcc dot gnu.org 2012-11-05 9:22 ` ubizjak at gmail dot com 2012-11-05 18:52 ` rsandifo at gcc dot gnu.org 2012-11-05 18:55 ` rsandifo at gcc dot gnu.org 2012-11-05 18:59 ` [Bug target/55204] " rsandifo 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-55204-4@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: linkBe 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).