public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65593] New: [5 Regression] internal compiler error: in extract_insn, at recog.c:2343 Date: Fri, 27 Mar 2015 06:15:00 -0000 [thread overview] Message-ID: <bug-65593-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65593 Bug ID: 65593 Summary: [5 Regression] internal compiler error: in extract_insn, at recog.c:2343 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com On Linux/x86-64, r221697 gave: [hjl@gnu-35 gcc-test-spec]$ ./usr/bin/gcc -S -fPIE -O2 -o /tmp/x.s src-trunk/gcc/testsuite/gcc.c-torture/compile/pr20928.c src-trunk/gcc/testsuite/gcc.c-torture/compile/pr20928.c: In function \u2018foo\u2019: src-trunk/gcc/testsuite/gcc.c-torture/compile/pr20928.c:10:1: error: unrecognizable insn: } ^ (insn 7 6 8 2 (set (reg/f:DI 88) (plus:DI (symbol_ref:DI ("bar") [flags 0x40] <var_decl 0x7ffff0dfac60 bar>) (reg:DI 89))) src-trunk/gcc/testsuite/gcc.c-torture/compile/pr20928.c:8 -1 (expr_list:REG_EQUAL (const:DI (plus:DI (symbol_ref:DI ("bar") [flags 0x40] <var_decl 0x7ffff0dfac60 bar>) (const_int 2147483648 [0x80000000]))) (nil))) src-trunk/gcc/testsuite/gcc.c-torture/compile/pr20928.c:10:1: internal compiler error: in extract_insn, at recog.c:2343 0xa9a2c8 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) ../../src-trunk/gcc/rtl-error.c:110 0xa9a2f9 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) ../../src-trunk/gcc/rtl-error.c:118 0xa68659 extract_insn(rtx_insn*) ../../src-trunk/gcc/recog.c:2343 0x86d1f3 instantiate_virtual_regs_in_insn ../../src-trunk/gcc/function.c:1598 0x86d1f3 instantiate_virtual_regs ../../src-trunk/gcc/function.c:1966 0x86d1f3 execute ../../src-trunk/gcc/function.c:2015 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. [hjl@gnu-35 gcc-test-spec]$
next reply other threads:[~2015-03-27 3:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-27 6:15 hjl.tools at gmail dot com [this message] 2015-03-27 6:59 ` [Bug target/65593] " hjl.tools at gmail dot com 2015-03-27 8:36 ` ubizjak at gmail dot com 2015-03-27 9:13 ` rguenth at gcc dot gnu.org 2015-03-27 12:10 ` jakub at gcc dot gnu.org 2015-03-27 13:53 ` jakub at gcc dot gnu.org 2015-03-27 17:51 ` jakub at gcc dot gnu.org 2015-03-27 18:01 ` 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-65593-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).