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: Wed, 08 May 2024 16:39:29 +0000 [thread overview] Message-ID: <bug-114810-4-fCwUFa6YKb@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 #17 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:2f00e6caca1a14dfe26e94f608e9d79a787ebe08 commit r15-330-g2f00e6caca1a14dfe26e94f608e9d79a787ebe08 Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Wed May 8 10:39:04 2024 -0400 [PR114810][LRA]: Recognize alternatives with lack of available registers for insn and demote them. PR114810 was fixed in machine-dependent way. This patch is a fix of the PR on LRA side. LRA chose alternative with constraints `&r,r,ro` on i686 when all operands of DImode and there are only 6 available general regs. The patch recognizes such case and significantly increase the alternative cost. It does not reject alternative completely. So the fix is safe but it might not work for all potentially possible cases of registers lack as register classes can have any relations including subsets and intersections. gcc/ChangeLog: PR target/114810 * lra-constraints.cc (process_alt_operands): Calculate union reg class for the alternative, peak matched regs and required reload regs. Recognize alternatives with lack of available registers and make them costly. Add debug print about this case.
prev parent reply other threads:[~2024-05-08 16:39 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 2024-04-23 21:31 ` jakub at gcc dot gnu.org 2024-05-08 16:39 ` cvs-commit at gcc dot gnu.org [this message]
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-fCwUFa6YKb@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).