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/98092] New: [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) Date: Wed, 02 Dec 2020 05:32:19 +0000 [thread overview] Message-ID: <bug-98092-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98092 Bug ID: 98092 Summary: [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) Product: gcc Version: 11.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: owerpc-*-linux-gnu gcc-11.0.0-alpha20201129 snapshot (g:bb67ad5cff58a707aaae645d4f45a913d8511c86) ICEs when compiling the following testcase, reduced from gcc/testsuite/gcc.target/powerpc/bcd-4.c, w/ -mcpu=power9 -ffinite-math-only: int h9 (__attribute__ ((altivec (vector__))) char un) { return (__builtin_vec_bcdinvalid (un)); } % powerpc-e300c3-linux-gnu-gcc-11.0.0 -mcpu=power9 -ffinite-math-only -c n1uis1ie.c n1uis1ie.c: In function 'h9': n1uis1ie.c:5:1: error: unrecognizable insn: 5 | } | ^ (insn 8 7 11 2 (set (reg:SI 118 [ _3 ]) (unordered:SI (reg:CCFP 106 6) (const_int 0 [0]))) "n1uis1ie.c":4:10 -1 (nil)) during RTL pass: vregs n1uis1ie.c:5:1: internal compiler error: in extract_insn, at recog.c:2315 0x68050a _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/rtl-error.c:108 0x68052a _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/rtl-error.c:116 0x67ebf3 extract_insn(rtx_insn*) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/recog.c:2315 0xacbbe1 instantiate_virtual_regs_in_insn /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/function.c:1609 0xacbbe1 instantiate_virtual_regs /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/function.c:1979 0xacbbe1 execute /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201129/work/gcc-11-20201129/gcc/function.c:2028
next reply other threads:[~2020-12-02 5:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-02 5:32 asolokha at gmx dot com [this message] 2020-12-02 8:24 ` [Bug target/98092] " rguenth at gcc dot gnu.org 2021-01-14 10:59 ` rguenth at gcc dot gnu.org 2021-01-22 12:46 ` jakub at gcc dot gnu.org 2021-01-22 20:57 ` cel at us dot ibm.com 2021-01-23 1:14 ` segher at gcc dot gnu.org 2021-03-05 14:02 ` jakub at gcc dot gnu.org 2021-03-16 18:17 ` [Bug target/98092] [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) since r11-4623 jakub at gcc dot gnu.org 2021-03-16 18:27 ` segher at gcc dot gnu.org 2021-03-16 19:22 ` cvs-commit at gcc dot gnu.org 2021-03-16 19:25 ` jakub 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-98092-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).