public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106933] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-2049-g6f94923dea21bd92 Date: Wed, 14 Sep 2022 11:39:54 +0000 [thread overview] Message-ID: <bug-106933-4-t02V1qCwCF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106933-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106933 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com --- Comment #2 from Roger Sayle <roger at nextmovesoftware dot com> --- Something very odd is going on. foo.simdclone.2 contains a *cmpti_doubleword instruction, that is defined using define_insn_and_split to be split pre-reload. For some reason, this isn't getting split during the split1 pass, but continues through reload until things finally fail in cprop_hardreg. Interestingly the corresponding instruction is correctly split in simdclone.0 and simdclone.1. The .293e.split1 file contains (much redacted)... ;; Function foo.simdclone.0 Splitting with gen_split_2 (i386.md:1511) deleting insn with uid = 16. ;; Function foo.simdclone.1 Splitting with gen_split_2 (i386.md:1511) deleting insn with uid = 22. ;; Function foo.simdclone.2 i.e. no splits are performed on foo.simdclone.2, but they are on simdclone.0 and simdclone.1. Perhaps an off-by-one error? I'll investigate further, but I doubt this is an issue in the i386.md machine description; the ((simd)) attribute is interacting strangely with the split pass.
next prev parent reply other threads:[~2022-09-14 11:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 18:49 [Bug target/106933] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) asolokha at gmx dot com 2022-09-13 19:23 ` [Bug target/106933] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-2049-g6f94923dea21bd92 marxin at gcc dot gnu.org 2022-09-14 6:25 ` rguenth at gcc dot gnu.org 2022-09-14 11:39 ` roger at nextmovesoftware dot com [this message] 2022-09-14 12:35 ` roger at nextmovesoftware dot com 2022-10-06 16:03 ` asolokha at gmx dot com 2022-10-06 17:18 ` hjl.tools at gmail dot com 2022-10-18 8:45 ` rguenth at gcc dot gnu.org 2022-10-21 18:53 ` hjl.tools at gmail dot com 2022-12-01 12:49 ` jakub at gcc dot gnu.org 2022-12-23 9:52 ` cvs-commit at gcc dot gnu.org 2022-12-24 17:16 ` roger at nextmovesoftware 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-106933-4-t02V1qCwCF@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).