From: Jeff Law <law@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
Peter Bergner <bergner@vnet.ibm.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Vladimir Makarov <vmakarov@redhat.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH] Fix aarch64 fallout of [PATCH, LRA] Fix PR rtl-optimization 77289, LRA matching constraint problem
Date: Tue, 13 Sep 2016 20:03:00 -0000 [thread overview]
Message-ID: <f86a6507-2775-773a-5ad5-92f4cfa1be6c@redhat.com> (raw)
In-Reply-To: <AM4PR0701MB21620B0A84C1D7F82A0DC706E4FF0@AM4PR0701MB2162.eurprd07.prod.outlook.com>
On 09/12/2016 07:43 AM, Bernd Edlinger wrote:
> Hi,
>
> the attached patch boot-straps and reg-tests cleanly
> on x86_64-pc-linux-gnu, powerpc and aarch64 targets.
>
> Is it OK for trunk?
>
>
> Thanks
> Bernd.
>
>
> patch-pr77289.diff
>
>
> 2016-09-12 Bernd Edlinger <bernd.edlinger@hotmail.de>
>
> PR rtl-optimization/77289
> * lra-constraints.c (get_final_hard_regno): Removed.
> (get_hard_regno): Add new parameter final_p.
> (get_reg_class): Directly call lra_get_elimination_hard_regno.
> (operands_match_p): Adjust call to get_hard_regno.
> (uses_hard_regs_p): Likewise.
> (process_alt_operands): Likewise.
A bit painful to follow as there's cleanup mixed in with the bugfix.
Thanks for pointing out the key change in the follow-up, that helped
considerably.
OK.
jeff
>
prev parent reply other threads:[~2016-09-13 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:53 Bernd Edlinger
2016-09-11 21:11 ` Peter Bergner
2016-09-12 13:24 ` Kyrill Tkachov
2016-09-12 14:05 ` [PATCH] Fix aarch64 fallout of " Bernd Edlinger
2016-09-12 21:54 ` Jeff Law
2016-09-12 22:06 ` Bernd Edlinger
2016-09-13 20:03 ` Jeff Law [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=f86a6507-2775-773a-5ad5-92f4cfa1be6c@redhat.com \
--to=law@redhat.com \
--cc=bergner@vnet.ibm.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=pinskia@gmail.com \
--cc=vmakarov@redhat.com \
--cc=wschmidt@linux.vnet.ibm.com \
/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: link
Be 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).