public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107322] New: ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with __bf16 compare Date: Wed, 19 Oct 2022 18:39:31 +0000 [thread overview] Message-ID: <bug-107322-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107322 Bug ID: 107322 Summary: ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with __bf16 compare 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: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 53731 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53731&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -fexcess-precision=16 -O testcase.c testcase.c: In function 'foo': testcase.c:8:1: error: unrecognizable insn: 8 | } | ^ (insn 7 6 9 2 (set (reg:CCFP 17 flags) (compare:CCFP (reg:BF 88) (reg:BF 87))) "testcase.c":7:5 -1 (nil)) during RTL pass: vregs testcase.c:8:1: internal compiler error: in extract_insn, at recog.cc:2791 0x78376b _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /repo/gcc-trunk/gcc/rtl-error.cc:108 0x7837e7 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /repo/gcc-trunk/gcc/rtl-error.cc:116 0x77239c extract_insn(rtx_insn*) /repo/gcc-trunk/gcc/recog.cc:2791 0x1043ee9 instantiate_virtual_regs_in_insn /repo/gcc-trunk/gcc/function.cc:1611 0x1043ee9 instantiate_virtual_regs /repo/gcc-trunk/gcc/function.cc:1985 0x1043ee9 execute /repo/gcc-trunk/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. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r13-3383-20221019140533-g47684e58edc-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r13-3383-20221019140533-g47684e58edc-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.0.0 20221019 (experimental) (GCC)
next reply other threads:[~2022-10-19 18:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-19 18:39 zsojka at seznam dot cz [this message] 2022-10-20 8:44 ` [Bug target/107322] " marxin at gcc dot gnu.org 2022-10-20 8:52 ` crazylht at gmail dot com 2022-10-20 10:35 ` jakub at gcc dot gnu.org 2022-10-21 16:35 ` cvs-commit at gcc dot gnu.org 2023-11-30 10:44 ` liuhongt 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-107322-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).