public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112313] New: [14 Regression] GCN target 'gcc.dg/pr111082.c' ICE, 'during RTL pass: vregs': 'error: unrecognizable insn' Date: Tue, 31 Oct 2023 11:54:43 +0000 [thread overview] Message-ID: <bug-112313-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112313 Bug ID: 112313 Summary: [14 Regression] GCN target 'gcc.dg/pr111082.c' ICE, 'during RTL pass: vregs': 'error: unrecognizable insn' Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org CC: ams at gcc dot gnu.org, jules at gcc dot gnu.org Target Milestone: --- Target: GCN (Assuming my tacking is to be believed) something in Git commit r14-2060-gad5ab848cc487b3f7fd82c7cb3c408747bd10422..r14-3575-g7f2ed06ddc825e8a4e0edfd1d66b5156e6dc1d34 triggers a new GCN target ICE (tested '-march=gfx90a'): [...]/gcc/testsuite/gcc.dg/pr111082.c: In function 'minarray2': [...]/gcc/testsuite/gcc.dg/pr111082.c:10:1: error: unrecognizable insn: (insn 10 9 11 2 (set (reg:V2DI 433) (smin:V2DI (reg:V2DI 434) (reg:V2DI 430))) -1 (nil)) during RTL pass: vregs [...]/gcc/testsuite/gcc.dg/pr111082.c:10:1: internal compiler error: in extract_insn, at recog.cc:2791 0x74b91f _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) [...]/gcc/rtl-error.cc:108 0x74b9a0 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) [...]/gcc/rtl-error.cc:116 0xed182e extract_insn(rtx_insn*) [...]/gcc/recog.cc:2791 0xb42cfc instantiate_virtual_regs_in_insn [...]/gcc/function.cc:1610 0xb42cfc instantiate_virtual_regs [...]/gcc/function.cc:1983 0xb42cfc execute [...]/gcc/function.cc:2030
next reply other threads:[~2023-10-31 11:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-31 11:54 tschwinge at gcc dot gnu.org [this message] 2023-11-02 8:26 ` [Bug target/112313] " rguenth at gcc dot gnu.org 2023-11-10 10:40 ` burnus at gcc dot gnu.org 2023-11-10 10:47 ` ams 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-112313-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).