public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106450] [13 Regression] ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn) Date: Tue, 26 Jul 2022 20:52:25 +0000 [thread overview] Message-ID: <bug-106450-4-aO9NcSUOwi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106450 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|--- |13.0 Last reconfirmed| |2022-07-26 Status|UNCONFIRMED |NEW CC| |roger at nextmovesoftware dot com --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- timode_remove_non_convertible_regs should be changed to handle all new operations like (insn 16 15 17 5 (parallel [ (set (reg:TI 92) (ior:TI (reg:TI 91) (reg/v:TI 87 [ uninitialized ]))) (clobber (reg:CC 17 flags)) ]) "x.c":10:5 578 {*iorti3_doubleword}
next prev parent reply other threads:[~2022-07-26 20:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-26 18:44 [Bug target/106450] New: " asolokha at gmx dot com 2022-07-26 20:52 ` hjl.tools at gmail dot com [this message] 2022-07-27 8:30 ` [Bug target/106450] [13 Regression] 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-27 11:35 ` roger at nextmovesoftware dot com 2022-07-31 7:36 ` roger at nextmovesoftware dot com 2022-07-31 20:47 ` cvs-commit at gcc dot gnu.org 2022-08-01 22: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-106450-4-aO9NcSUOwi@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).