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 middle-end/113354] [14 Regression] : unable to find a register to spill on mips Date: Mon, 15 Jan 2024 15:26:02 +0000 [thread overview] Message-ID: <bug-113354-4-Bew4O9T4MD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113354-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113354 --- Comment #4 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:76bc70387d936e3c929368c265ce71e8b239e7b7 commit r14-7248-g76bc70387d936e3c929368c265ce71e8b239e7b7 Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Mon Jan 15 10:19:39 2024 -0500 [PR113354][LRA]: Fixing LRA failure on building MIPS GCC My recent patch for PR112918 triggered a hidden bug in LRA on MIPS. A pseudo is matched to a register constraint and assigned to a hard registers at the first constraint sub-pass but later it is matched to X constraint. Keeping this pseudo in the register (MD0) prevents to use the same register for another pseudo in the insn and this results in LRA failure. The patch fixes this by spilling the pseudo at the constraint subpass when the chosen alternative constraint not require hard register anymore. gcc/ChangeLog: PR middle-end/113354 * lra-constraints.cc (curr_insn_transform): Spill pseudo only used in the insn if the corresponding operand does not require hard register anymore.
next prev parent reply other threads:[~2024-01-15 15:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 12:28 [Bug middle-end/113354] New: Regression/14: " syq at gcc dot gnu.org 2024-01-12 14:02 ` [Bug middle-end/113354] " syq at gcc dot gnu.org 2024-01-12 18:34 ` vmakarov at gcc dot gnu.org 2024-01-13 0:46 ` [Bug middle-end/113354] [14 Regression] : " pinskia at gcc dot gnu.org 2024-01-15 15:26 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-17 9:44 ` syq 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-113354-4-Bew4O9T4MD@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).