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/107970] New: ICE in extract_insn, at recog.cc:2791 since r13-2730-gd0c73b6c85677e67
Date: Mon, 05 Dec 2022 08:51:42 +0000 [thread overview]
Message-ID: <bug-107970-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
Bug ID: 107970
Summary: ICE in extract_insn, at recog.cc:2791 since
r13-2730-gd0c73b6c85677e67
Product: gcc
Version: 13.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: crazylht at gmail dot com
Target Milestone: ---
Host: x86_64-linux-gnu
The following crashes:
$ cat ice.i
float *foo_p;
void
foo(float *__restrict q) {
foo_p[0] = __builtin_truncf(q[0]);
foo_p[1] = __builtin_truncf(q[1]);
}
$ gcc -m32 -Ofast -m3dnowa -mavx512vpopcntdq ice.i -c
ice.i: In function ‘foo’:
ice.i:7:1: error: unrecognizable insn:
7 | }
| ^
(insn 7 6 8 2 (set (reg:V2SF 84 [ vect__3.8 ])
(unspec:V2SF [
(reg:V2SF 86 [ vect__1.7 ])
(const_int 11 [0xb])
] UNSPEC_ROUND)) "ice.i":5:14 -1
(nil))
during RTL pass: vregs
ice.i:7:1: internal compiler error: in extract_insn, at recog.cc:2791
0x75acd4 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/Programming/gcc/gcc/rtl-error.cc:108
0x75acf0 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/Programming/gcc/gcc/rtl-error.cc:116
0x7592b5 extract_insn(rtx_insn*)
/home/marxin/Programming/gcc/gcc/recog.cc:2791
0xb88100 instantiate_virtual_regs_in_insn
/home/marxin/Programming/gcc/gcc/function.cc:1611
0xb88100 instantiate_virtual_regs
/home/marxin/Programming/gcc/gcc/function.cc:1985
0xb88100 execute
/home/marxin/Programming/gcc/gcc/function.cc:2034
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2022-12-05 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:51 marxin at gcc dot gnu.org [this message]
2022-12-05 8:51 ` [Bug target/107970] " marxin at gcc dot gnu.org
2022-12-06 2:42 ` [Bug target/107970] [13 Regression] " crazylht at gmail dot com
2022-12-06 11:29 ` jakub at gcc dot gnu.org
2022-12-07 1:20 ` cvs-commit at gcc dot gnu.org
2022-12-07 1:21 ` crazylht at gmail dot com
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-107970-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).