public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96273] New: ice in extract_insn, at recog.c:2294, unrecognizable insn: Date: Tue, 21 Jul 2020 20:34:07 +0000 [thread overview] Message-ID: <bug-96273-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96273 Bug ID: 96273 Summary: ice in extract_insn, at recog.c:2294, unrecognizable insn: Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 48911 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48911&action=edit gzipped C++ source code The attached C++ code does this with today's gcc trunk: splat.cpp:1637:1: error: unrecognizable insn: (insn 1137 1136 1138 163 (set (mem/v:BLK (scratch:DI) [0 A8]) (unspec:BLK [ (mem/v:BLK (scratch:DI) [0 A8]) ] UNSPEC_MFENCE)) -1 (nil)) during RTL pass: vregs splat.cpp:1637:1: internal compiler error: in extract_insn, at recog.c:2294 0xef8b46 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) ../../trunk.git/gcc/rtl-error.c:108 0xef8b6b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) ../../trunk.git/gcc/rtl-error.c:116 0xebf423 extract_insn(rtx_insn*) ../../trunk.git/gcc/recog.c:2294 Flags -O3 -march=native required. native is Piledriver. I'll have a go at reducing the code. This code used to work at date 20200719, so someone has broken something in the last day or two.
next reply other threads:[~2020-07-21 20:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 20:34 dcb314 at hotmail dot com [this message] 2020-07-21 21:08 ` [Bug target/96273] " dcb314 at hotmail dot com 2020-07-22 6:50 ` crazylht at gmail dot com 2020-07-22 6:52 ` ubizjak 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-96273-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).