public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrealign -O2 -mbmi -fno-exceptions -fno-plt Date: Mon, 22 Apr 2024 19:23:48 +0000 [thread overview] Message-ID: <bug-114810-4-xfvABlMUxh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114810-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 --- Comment #4 from Uroš Bizjak <ubizjak at gmail dot com> --- An interesting observation, when the insn is defined only with problematic alternative: (define_insn_and_split "*andn<dwi>3_doubleword_bmi" [(set (match_operand:<DWI> 0 "register_operand" "=&r") (and:<DWI> (not:<DWI> (match_operand:<DWI> 1 "register_operand" "r")) (match_operand:<DWI> 2 "nonimmediate_operand" "ro"))) (clobber (reg:CC FLAGS_REG))] the compilation succeeds, and a spill to memory is emitted: (insn 1170 65 1177 7 (set (mem/c:DI (plus:SI (reg/f:SI 6 bp) (const_int -168 [0xffffffffffffff58])) [71 %sfp+-144 S8 A64]) (reg:DI 0 ax [orig:217 _13 ] [217])) "pr114810.C":296:36 84 {*movdi_internal} (nil)) ... (insn 987 1154 1111 7 (parallel [ (set (reg:DI 3 bx [453]) (and:DI (not:DI (reg:DI 0 ax [452])) (mem/c:DI (plus:SI (reg/f:SI 6 bp) (const_int -168 [0xffffffffffffff58])) [71 %sfp+-144 S8 A64]))) (clobber (reg:CC 17 flags)) ]) "pr114810.C":296:6 703 {*andndi3_doubleword_bmi} (nil))
next prev parent reply other threads:[~2024-04-22 19:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 17:57 [Bug target/114810] New: " kocelfc at tutanota dot com 2024-04-22 17:58 ` [Bug target/114810] " kocelfc at tutanota dot com 2024-04-22 18:22 ` jakub at gcc dot gnu.org 2024-04-22 19:10 ` ubizjak at gmail dot com 2024-04-22 19:23 ` ubizjak at gmail dot com [this message] 2024-04-22 19:31 ` [Bug rtl-optimization/114810] " ubizjak at gmail dot com 2024-04-22 19:45 ` vmakarov at gcc dot gnu.org 2024-04-22 20:07 ` ubizjak at gmail dot com 2024-04-22 21:36 ` jakub at gcc dot gnu.org 2024-04-22 21:48 ` vmakarov at gcc dot gnu.org 2024-04-22 21:56 ` jakub at gcc dot gnu.org 2024-04-23 5:53 ` ubizjak at gmail dot com 2024-04-23 6:02 ` ubizjak at gmail dot com 2024-04-23 12:29 ` jakub at gcc dot gnu.org 2024-04-23 12:46 ` ubizjak at gmail dot com 2024-04-23 21:31 ` cvs-commit at gcc dot gnu.org 2024-04-23 21:31 ` jakub at gcc dot gnu.org 2024-05-08 16:39 ` cvs-commit 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-114810-4-xfvABlMUxh@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).