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/104400] [12 Regression] v850e lra/reload failure after recent change Date: Fri, 11 Feb 2022 15:50:17 +0000 [thread overview] Message-ID: <bug-104400-4-h27dhLzG1B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104400-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104400 --- Comment #4 from CVS 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:274a4d29421e73c9b40c1641986c6ed904e20184 commit r12-7200-g274a4d29421e73c9b40c1641986c6ed904e20184 Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Fri Feb 11 09:52:14 2022 -0500 [PR104400] LRA: Modify exclude start hard register calculation for insn alternative v850 target has an interesting insn alternative constraint 'e!r' where e denotes even general regs and e is a subset of r. We cannot just make union of exclude start hard registers for e and r and should use only exclude start hard registers of r. The following patch implements this. gcc/ChangeLog: PR rtl-optimization/104400 * lra-constraints.cc (process_alt_operands): Don't make union of this_alternative_exclude_start_hard_regs when reg class in insn alternative covers other reg classes in the same alternative. gcc/testsuite/ChangeLog: PR rtl-optimization/104400 * gcc.target/v850/pr104400.c: New. * gcc.target/v850/v850.exp: New.
next prev parent reply other threads:[~2022-02-11 15:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-05 18:57 [Bug rtl-optimization/104400] New: " law at gcc dot gnu.org 2022-02-07 7:51 ` [Bug rtl-optimization/104400] " rguenth at gcc dot gnu.org 2022-02-09 14:47 ` vmakarov at gcc dot gnu.org 2022-02-09 17:14 ` law at gcc dot gnu.org 2022-02-10 15:22 ` vmakarov at gcc dot gnu.org 2022-02-11 15:50 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-11 16:57 ` law 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-104400-4-h27dhLzG1B@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).