public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94435] New: ICE in extract_insn, at recog.c:2294
Date: Wed, 01 Apr 2020 09:16:26 +0000 [thread overview]
Message-ID: <bug-94435-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94435
Bug ID: 94435
Summary: ICE in extract_insn, at recog.c:2294
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
Target: aarch64-linux-gnu
Once Jakub added a new test-case I see:
$ ./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr94368.c
-moutline-atomics -c
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr94368.c: In function ‘bar’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr94368.c:25:1: error:
unrecognizable insn:
25 | }
| ^
(insn 62 61 63 8 (set (reg:CC 66 cc)
(compare:CC (reg:SI 0 x0)
(reg:HI 122)))
"/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr94368.c":23:7 -1
(nil))
during RTL pass: vregs
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr94368.c:25:1: internal
compiler error: in extract_insn, at recog.c:2294
0x119b89f _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/Programming/gcc2/gcc/rtl-error.c:108
0x119b8e0 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/Programming/gcc2/gcc/rtl-error.c:116
0x114a983 extract_insn(rtx_insn*)
/home/marxin/Programming/gcc2/gcc/recog.c:2294
0xdb0281 instantiate_virtual_regs_in_insn
/home/marxin/Programming/gcc2/gcc/function.c:1607
0xdb1859 instantiate_virtual_regs
/home/marxin/Programming/gcc2/gcc/function.c:1977
0xdb1924 execute
/home/marxin/Programming/gcc2/gcc/function.c:2026
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
The issues started with r10-3301-g3950b229a5ed6710f30241c2ddc3c74909bf4740
where -moutline-atomics was added.
next reply other threads:[~2020-04-01 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 9:16 marxin at gcc dot gnu.org [this message]
2020-04-01 9:16 ` [Bug target/94435] " marxin at gcc dot gnu.org
2020-04-01 9:39 ` jakub at gcc dot gnu.org
2020-04-01 21:01 ` [Bug target/94435] [9/10 Regression] " pinskia at gcc dot gnu.org
2020-04-02 10:55 ` cvs-commit at gcc dot gnu.org
2020-04-02 10:57 ` cvs-commit at gcc dot gnu.org
2020-04-02 10:59 ` cvs-commit at gcc dot gnu.org
2020-04-02 11:00 ` jakub at gcc dot gnu.org
2020-04-22 16:10 ` cvs-commit 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-94435-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: 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).