public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manuel.lauss at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113048] [13/14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1862 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -march=cascadelake since r13-1716 Date: Fri, 05 Jan 2024 14:33:20 +0000 [thread overview] Message-ID: <bug-113048-4-uFYUiaPq7m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113048-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113048 --- Comment #6 from Manuel Lauss <manuel.lauss at googlemail dot com> --- After be977db17c91ad6627dee70a1904a95d229aa1be I don't see this ICE any longer on either x64 or mips bootstrap.
next prev parent reply other threads:[~2024-01-05 14:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-17 6:57 [Bug target/113048] New: [13/14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1862 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -march=cascadelake zsojka at seznam dot cz 2023-12-18 8:21 ` [Bug target/113048] " rguenth at gcc dot gnu.org 2023-12-20 12:04 ` manuel.lauss at googlemail dot com 2024-01-04 12:03 ` [Bug target/113048] [13/14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1862 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -march=cascadelake since r13-1716 jakub at gcc dot gnu.org 2024-01-04 12:04 ` jakub at gcc dot gnu.org 2024-01-05 9:59 ` [Bug rtl-optimization/113048] " ubizjak at gmail dot com 2024-01-05 14:33 ` manuel.lauss at googlemail dot com [this message] 2024-01-15 15:55 ` vmakarov at gcc dot gnu.org 2024-01-15 16:08 ` ubizjak at gmail dot com 2024-01-15 16:36 ` cvs-commit at gcc dot gnu.org 2024-01-15 16:37 ` [Bug rtl-optimization/113048] [13 " jakub at gcc dot gnu.org 2024-05-21 9:18 ` jakub 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-113048-4-uFYUiaPq7m@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).