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/106347] [13 Regression] ICE in ix86_output_ssemov, at config/i386/i386.cc:5565, or ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn) since r13-1607-gc3ed9e0d6e96d869 Date: Tue, 19 Jul 2022 11:26:02 +0000 [thread overview] Message-ID: <bug-106347-4-T7WKyQb1dJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106347-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106347 --- Comment #4 from Roger Sayle <roger at nextmovesoftware dot com> --- No, it's not PR 106278 that this PR is similar to (which concerned REG_EQUAL notes and is now fixed), but PR 106303 (which concerns STV converting some mentions of a TImode register/memory, and not others, due to data flow analysis and rtx sharing) which is still open/unresolved. My apologies for the inconvenience, figuring out why the pre-existing STV infrastructure is making some of these counter-intuitive decisions, and what the intended behavior should be, is taking some time. Obviously -mno-stv is a work around.
next prev parent reply other threads:[~2022-07-19 11:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-18 19:24 [Bug target/106347] New: [13 Regression] ICE in ix86_output_ssemov, at config/i386/i386.cc:5565, or ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn) asolokha at gmx dot com 2022-07-19 6:52 ` [Bug target/106347] " rguenth at gcc dot gnu.org 2022-07-19 7:43 ` crazylht at gmail dot com 2022-07-19 7:45 ` crazylht at gmail dot com 2022-07-19 10:21 ` [Bug target/106347] [13 Regression] ICE in ix86_output_ssemov, at config/i386/i386.cc:5565, or ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn) since r13-1607-gc3ed9e0d6e96d869 marxin at gcc dot gnu.org 2022-07-19 11:26 ` roger at nextmovesoftware dot com [this message] 2022-07-20 16:35 ` roger at nextmovesoftware dot com 2022-07-24 11:24 ` cvs-commit at gcc dot gnu.org 2022-07-25 16:59 ` 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-106347-4-T7WKyQb1dJ@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).