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/104003] New: [12 Regression] ICE in extract_insn, at recog.c:2769 since r12-6488-g820ac79e8448ad6c
Date: Thu, 13 Jan 2022 09:29:03 +0000 [thread overview]
Message-ID: <bug-104003-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104003
Bug ID: 104003
Summary: [12 Regression] ICE in extract_insn, at recog.c:2769
since r12-6488-g820ac79e8448ad6c
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: ubizjak at gmail dot com
Target Milestone: ---
The following fails:
$ g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.target/i386/pr103861-1.C
-mxop -c
/home/marxin/Programming/gcc/gcc/testsuite/g++.target/i386/pr103861-1.C: In
function ‘__v2qu uu(__v2qu, __v2qu)’:
/home/marxin/Programming/gcc/gcc/testsuite/g++.target/i386/pr103861-1.C:11:60:
error: unrecognizable insn:
11 | __v2qu uu (__v2qu a, __v2qu b) { return (a > b) ? au : bu; }
| ^
(insn 12 11 15 2 (set (reg:V2QI 84 [ _7 ])
(if_then_else:V2QI (reg:V2QI 84 [ _7 ])
(reg:V2QI 82 [ au.0_2 ])
(reg:V2QI 83 [ bu.1_3 ])))
"/home/marxin/Programming/gcc/gcc/testsuite/g++.target/i386/pr103861-1.C":11:56
-1
(nil))
during RTL pass: vregs
/home/marxin/Programming/gcc/gcc/testsuite/g++.target/i386/pr103861-1.C:11:60:
internal compiler error: in extract_insn, at recog.c:2769
0x218a6a8 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:108
0x218a6ca _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:116
0x21584d3 extract_insn(rtx_insn*)
/home/marxin/Programming/gcc/gcc/recog.c:2769
0x1c99f83 instantiate_virtual_regs_in_insn
/home/marxin/Programming/gcc/gcc/function.c:1611
0x1c99f83 instantiate_virtual_regs
/home/marxin/Programming/gcc/gcc/function.c:1985
0x1c99f83 execute
/home/marxin/Programming/gcc/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:[~2022-01-13 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 9:29 marxin at gcc dot gnu.org [this message]
2022-01-13 10:15 ` [Bug target/104003] " rguenth at gcc dot gnu.org
2022-01-13 10:42 ` ubizjak at gmail dot com
2022-01-13 10:57 ` ubizjak at gmail dot com
2022-01-13 16:20 ` cvs-commit at gcc dot gnu.org
2022-01-13 16:21 ` ubizjak 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-104003-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).