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/102941] New: ICE in extract_insn, at recog.c:2769 with -ftrivial-auto-var-init=pattern
Date: Tue, 26 Oct 2021 06:39:58 +0000 [thread overview]
Message-ID: <bug-102941-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102941
Bug ID: 102941
Summary: ICE in extract_insn, at recog.c:2769 with
-ftrivial-auto-var-init=pattern
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: qing.zhao at oracle dot com
Target Milestone: ---
Host: x86_64-linux-gnu
Target: aarch64-linux-gnu
The following happens:
$ cat asm-flag.c
int test_cmpu_x;
void
test_cmpu_y() {
long le;
__asm__("cmp %"
"[x], %"
"[y]"
: "=@ccls"(le)
: [x] ""(test_cmpu_x), [y] ""(test_cmpu_y));
}
$ aarch64-linux-gnu-gcc asm-flag.c -c
$ aarch64-linux-gnu-gcc asm-flag.c -c -ftrivial-auto-var-init=pattern
asm-flag.c: In function ‘test_cmpu_y’:
asm-flag.c:11:1: error: unrecognizable insn:
11 | }
| ^
(insn 13 14 0 2 (set (mem/c:DI (plus:DI (reg/f:DI 87 virtual-stack-vars)
(const_int -8 [0xfffffffffffffff8])) [2 le+0 S8 A64])
(leu:DI (reg:CC 66 cc)
(const_int 0 [0]))) "asm-flag.c":6:3 -1
(nil))
during RTL pass: vregs
asm-flag.c:11:1: internal compiler error: in extract_insn, at recog.c:2769
0x6a7b6b _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/rtl-error.c:108
0x6a7b87 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/rtl-error.c:116
0x6a6fa4 extract_insn(rtx_insn*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/recog.c:2769
0x945a6d instantiate_virtual_regs_in_insn
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/function.c:1611
0x945a6d instantiate_virtual_regs
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/function.c:1985
0x945a6d execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/function.c:2034
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.
next reply other threads:[~2021-10-26 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 6:39 marxin at gcc dot gnu.org [this message]
2021-10-26 6:40 ` [Bug target/102941] " marxin at gcc dot gnu.org
2021-10-26 6:42 ` pinskia at gcc dot gnu.org
2021-10-26 6:49 ` [Bug target/102941] ICE in extract_insn with ccflags output from inline-asm and var with address taken pinskia at gcc dot gnu.org
2021-10-26 6:54 ` pinskia at gcc dot gnu.org
2021-10-26 7:08 ` pinskia at gcc dot gnu.org
2021-10-26 7:12 ` pinskia at gcc dot gnu.org
2021-10-26 7:32 ` pinskia at gcc dot gnu.org
2021-10-26 9:45 ` pinskia at gcc dot gnu.org
2021-10-26 14:42 ` qinzhao at gcc dot gnu.org
2021-10-26 14:50 ` pinskia at gcc dot gnu.org
2022-01-07 22:07 ` cvs-commit at gcc dot gnu.org
2022-01-07 22:08 ` pinskia 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-102941-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).