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/106887] New: ICE in extract_insn, at recog.cc:2791 since r13-2111-g6910cad55ffc330d Date: Thu, 08 Sep 2022 08:42:45 +0000 [thread overview] Message-ID: <bug-106887-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106887 Bug ID: 106887 Summary: ICE in extract_insn, at recog.cc:2791 since r13-2111-g6910cad55ffc330d Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: lingling.kong7 at gmail dot com Target Milestone: --- The following crashes: $ cat bf16.i typedef __bf16 v16bf __attribute__((__vector_size__(32))); void vec_init_dup_v16bf() { __bf16 a1; (v16bf){a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1, a1}; } $ gcc bf16.i -c -mf16c bf16.i: In function ‘vec_init_dup_v16bf’: bf16.i:7:1: error: unrecognizable insn: 7 | } | ^ (insn 11 10 12 2 (set (reg:V16BF 83) (vec_concat:V16BF (reg:V16QI 84) (reg:V16QI 84))) "bf16.i":6:10 -1 (nil)) during RTL pass: vregs bf16.i:7:1: internal compiler error: in extract_insn, at recog.cc:2791 0x77971c _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /home/marxin/Programming/gcc/gcc/rtl-error.cc:108 0x77973e _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /home/marxin/Programming/gcc/gcc/rtl-error.cc:116 0x77794b extract_insn(rtx_insn*) /home/marxin/Programming/gcc/gcc/recog.cc:2791 0xbf1315 instantiate_virtual_regs_in_insn /home/marxin/Programming/gcc/gcc/function.cc:1611 0xbf1315 instantiate_virtual_regs /home/marxin/Programming/gcc/gcc/function.cc:1985 0xbf1315 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-09-08 8:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-08 8:42 marxin at gcc dot gnu.org [this message] 2022-09-08 8:42 ` [Bug target/106887] " marxin at gcc dot gnu.org 2022-09-15 2:25 ` asolokha at gmx dot com 2022-09-20 1:30 ` cvs-commit at gcc dot gnu.org 2023-04-26 6:56 ` rguenth at gcc dot gnu.org 2023-05-11 14:11 ` jamborm at gcc dot gnu.org 2023-05-30 13:12 ` jamborm 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-106887-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).