public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106933] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) Date: Tue, 13 Sep 2022 18:49:43 +0000 [thread overview] Message-ID: <bug-106933-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106933 Bug ID: 106933 Summary: [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) 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: asolokha at gmx dot com Target Milestone: --- Target: x86_64-unknown-linux-gnu gcc 13.0.0 20220911 snapshot (g:0ea5e3f4542832b8da016b152695e64a2a386309) ICEs when compiling the following testcase w/ -O2: short int bar (void); __int128 empty (void) { } __attribute__ ((simd)) int foo (__int128 *p) { int a = 0x80000000; *p = empty (); return *p == (a < bar ()); } % x86_64-unknown-linux-gnu-gcc-13.0.0 -O2 -c ylbcgrld.c ylbcgrld.c: In function 'foo.simdclone.2': ylbcgrld.c:17:1: error: unrecognizable insn: 17 | } | ^ (insn 73 72 74 3 (set (reg:CCZ 17 flags) (compare:CCZ (reg:V1TI 20 xmm0 [orig:82 D.2028 ] [82]) (const_int 1 [0x1]))) "ylbcgrld.c":16:13 -1 (expr_list:REG_DEAD (reg:V1TI 20 xmm0 [orig:82 D.2028 ] [82]) (nil))) during RTL pass: cprop_hardreg ylbcgrld.c:17:1: internal compiler error: in extract_insn, at recog.cc:2791 0x730822 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/rtl-error.cc:108 0x73083e _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/rtl-error.cc:116 0x72edc3 extract_insn(rtx_insn*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/recog.cc:2791 0xe4dc0b extract_constrain_insn(rtx_insn*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/recog.cc:2690 0xe58de6 copyprop_hardreg_forward_1 /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/regcprop.cc:826 0xe59fbf execute /var/tmp/portage/sys-devel/gcc-13.0.0_p20220911/work/gcc-13-20220911/gcc/regcprop.cc:1408
next reply other threads:[~2022-09-13 18:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 18:49 asolokha at gmx dot com [this message] 2022-09-13 19:23 ` [Bug target/106933] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-2049-g6f94923dea21bd92 marxin at gcc dot gnu.org 2022-09-14 6:25 ` rguenth at gcc dot gnu.org 2022-09-14 11:39 ` roger at nextmovesoftware dot com 2022-09-14 12:35 ` roger at nextmovesoftware dot com 2022-10-06 16:03 ` asolokha at gmx dot com 2022-10-06 17:18 ` hjl.tools at gmail dot com 2022-10-18 8:45 ` rguenth at gcc dot gnu.org 2022-10-21 18:53 ` hjl.tools at gmail dot com 2022-12-01 12:49 ` jakub at gcc dot gnu.org 2022-12-23 9:52 ` cvs-commit at gcc dot gnu.org 2022-12-24 17:16 ` roger at nextmovesoftware 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-106933-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).