public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sepotvin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109760] riscv Internal compiler error in extract_insn after addition of XTheadCondMov Date: Sun, 07 May 2023 17:57:15 +0000 [thread overview] Message-ID: <bug-109760-4-CZ0TWJr0RH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109760-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109760 --- Comment #1 from Stephane Potvin <sepotvin at gmail dot com> --- Slightly simpler reproduction program void b() { double c; for(;;) { void e(void*); e(c ? 0 : b); } } Which give the following error gcc -O2 -mcpu=sifive-u74 -c libimagequant.c.i libimagequant.c.i: In function ‘b’: libimagequant.c.i:7:1: error: unrecognizable insn: 7 | } | ^ (insn 7 6 8 2 (set (reg:DI 137) (if_then_else:DI (eq:DF (reg/v:DF 135 [ c ]) (reg:DF 138)) (reg:DI 139) (const_int 0 [0]))) -1 (nil)) during RTL pass: vregs libimagequant.c.i:7:1: internal compiler error: in extract_insn, at recog.cc:2791 0x27546d _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/gcc/rtl-error.cc:108 0x27548f _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/gcc/rtl-error.cc:116 0x6abbff extract_insn(rtx_insn*) /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/gcc/recog.cc:2791 0x4a790b instantiate_virtual_regs_in_insn /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/gcc/function.cc:1611 0x4a790b instantiate_virtual_regs /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/gcc/function.cc:1985 0x4a790b execute /usr/src/debug/sys-devel/gcc-13.1.0-r1/gcc-13.1.0/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://bugs.gentoo.org/> for instructions.
next prev parent reply other threads:[~2023-05-07 17:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-06 22:54 [Bug target/109760] New: " sepotvin at gmail dot com 2023-05-07 17:57 ` sepotvin at gmail dot com [this message] 2023-06-02 21:00 ` [Bug target/109760] " pinskia at gcc dot gnu.org 2024-03-06 18:04 ` law at gcc dot gnu.org 2024-03-06 18:23 ` law at gcc dot gnu.org 2024-03-07 17:39 ` sepotvin 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-109760-4-CZ0TWJr0RH@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).