public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/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: Tue, 23 Apr 2024 21:31:11 +0000 [thread overview] Message-ID: <bug-114810-4-qPvdNtAK7Y@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 #15 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:628c2221d38715a64f828e3635317293d150e001 commit r14-10099-g628c2221d38715a64f828e3635317293d150e001 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 23 23:30:27 2024 +0200 i386: Avoid =&r,r,r andn double-word alternative for ia32 [PR114810] As discussed in the PR, on ia32 with its 8 GPRs, where 1 is always fixed and other 2 often are as well having an alternative which needs 3 double-word registers is just too much for RA. The following patch splits that alternative into two, one with o is used even on ia32, but one with the 3x r is used just for -m64/-mx32. Tried to reduce the testcase further, but it wasn't easily possible. 2024-04-23 Jakub Jelinek <jakub@redhat.com> PR target/114810 * config/i386/i386.md (*andn<dwi>3_doubleword_bmi): Split the =&r,r,ro alternative into =&r,r,r enabled only for x64 and =&r,r,o. * g++.target/i386/pr114810.C: New test.
next prev parent reply other threads:[~2024-04-23 21:31 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 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 [this message] 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-qPvdNtAK7Y@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).