From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
ebotcazou@adacore.com
Subject: Re: [PATCH v2, rs6000] Fix PR72827 (ada bootstrap failure)
Date: Thu, 01 Sep 2016 14:44:00 -0000 [thread overview]
Message-ID: <0D3A2BA2-6DF8-4690-B0A4-A71F0919A8FA@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160901143231.GB9816@gate.crashing.org>
On Sep 1, 2016, at 9:32 AM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>
> On Wed, Aug 31, 2016 at 09:15:32PM -0500, Bill Schmidt wrote:
>> This patch (suggested by Michael Meissner) instead prevents the problem
>> by disallowing reg+reg addressing for TImode, allowing D-form addressing
>> to be used for the separate stores of the GPRs. This is not an ideal
>> permanent solution, because it disallows reg+reg addressing not only for
>> TImode in GPRs, but also for TImode in VSRs. Our intent is to work on a
>> solution to provide a scratch register via secondary reload, but this
>> may take some time. Thus I'd like to submit this patch as a short-term
>> solution for the bootstrap problem until then.
>>
>> I plan to do a performance evaluation of this patch for informational
>> purposes, but I don't expect much change, and the results won't affect
>> our choice to handle this properly in secondary reload.
>>
>> Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no
>> regressions, and the gnattools now build properly so that the ada
>> bootstrap succeeds. Is this ok for trunk?
>
> Yes please. Thanks,
r239938, thanks!
Bill
>
>
> Segher
>
prev parent reply other threads:[~2016-09-01 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 1:24 [PATCH, " Bill Schmidt
2016-08-31 6:20 ` Segher Boessenkool
2016-08-31 7:08 ` Eric Botcazou
2016-08-31 9:07 ` Segher Boessenkool
2016-09-06 21:31 ` Jeff Law
2016-09-06 23:02 ` Segher Boessenkool
2016-09-07 0:10 ` Jeff Law
2016-08-31 14:00 ` Bill Schmidt
2016-08-31 15:31 ` Eric Botcazou
2016-08-31 16:13 ` Bill Schmidt
2016-08-31 20:07 ` Bill Schmidt
2016-09-01 2:15 ` [PATCH v2, " Bill Schmidt
2016-09-01 7:21 ` Eric Botcazou
2016-09-01 14:32 ` Segher Boessenkool
2016-09-01 14:44 ` Bill Schmidt [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=0D3A2BA2-6DF8-4690-B0A4-A71F0919A8FA@linux.vnet.ibm.com \
--to=wschmidt@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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: 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).