From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>, nd <nd@arm.com>
Subject: Re: [PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
Date: Wed, 11 Jan 2017 17:19:00 -0000 [thread overview]
Message-ID: <AM4PR0701MB21627E52E5CEB739AF2ECA8CE4660@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <582e8637-664d-6426-36f8-3a83b30ae8f9@arm.com>
On 01/11/17 17:55, Richard Earnshaw (lists) wrote:
>
> Sorry for the delay getting around to this.
>
> I just tried this patch and found that it doesn't apply. Furthermore,
> there's not enough context in the rejected hunks for me to be certain
> which patterns you're trying to fix up.
>
> Could you do an update please?
>
Sure, I just gave up pinging, as we are rather late in stage 3
already...
So the current status is this:
I have the invalid code issue here; it is independent of the
optimization issues:
[PATCH, ARM] correctly encode the CC reg data flow
https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01562.html
Then I have the patch for splitting the most important
64bit patterns here:
[PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02796.html
and the follow-up patch that triggered the invalid code here:
[PATCH, ARM] Further improve stack usage in sha512, part 2 (PR 77308)
https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01563.html
In the last part I had initially this hunk,
- operands[2] = gen_lowpart (SImode, operands[2]);
+ if (can_create_pseudo_p ())
+ operands[2] = gen_reg_rtx (SImode);
+ else
+ operands[2] = gen_lowpart (SImode, operands[2]);
As Wilco pointed out that the else part is superfluous,
I already removed the gen_lowpart stuff locally.
All three parts should apply to trunk, only the last part
depends on both earlier patches.
Thanks
Bernd.
next prev parent reply other threads:[~2017-01-11 17:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 14:18 Bernd Edlinger
2016-11-25 11:30 ` Ramana Radhakrishnan
2016-11-28 19:42 ` Bernd Edlinger
[not found] ` <VI1PR0802MB2621FFBFA3252B40E5978C9F838D0@VI1PR0802MB2621.eurprd08.prod.outlook.com>
2016-11-29 21:37 ` Bernd Edlinger
[not found] ` <AM5PR0802MB261038521472515DDE3E58DA838D0@AM5PR0802MB2610.eurprd08.prod.outlook.com>
2016-11-30 12:01 ` Wilco Dijkstra
2016-11-30 17:01 ` Bernd Edlinger
2016-12-08 19:50 ` Bernd Edlinger
2017-01-11 16:55 ` Richard Earnshaw (lists)
2017-01-11 17:19 ` Bernd Edlinger [this message]
2017-04-29 19:17 ` [PING**2] " Bernd Edlinger
2017-05-12 16:51 ` [PING**3] " Bernd Edlinger
2017-06-01 16:01 ` [PING**4] " Bernd Edlinger
[not found] ` <bd5e03b1-860f-dd16-2030-9ce0f9a94c7c@hotmail.de>
2017-06-14 12:35 ` [PING**5] " Bernd Edlinger
[not found] ` <9a0fbb5d-9909-ef4d-6871-0cb4f7971bbb@hotmail.de>
2017-07-05 18:14 ` [PING**6] " Bernd Edlinger
2017-09-04 14:52 ` [PING**2] " Kyrill Tkachov
2017-09-05 8:47 ` Christophe Lyon
2017-09-05 14:25 ` Bernd Edlinger
2017-09-05 15:02 ` Wilco Dijkstra
2017-09-05 17:48 ` Bernd Edlinger
2017-09-05 17:53 ` Kyrill Tkachov
2017-09-05 18:20 ` Christophe Lyon
2017-09-06 7:35 ` Christophe Lyon
2017-09-05 21:28 ` Wilco Dijkstra
2017-09-06 9:31 ` Bernd Edlinger
2017-09-05 17:45 ` Kyrill Tkachov
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=AM4PR0701MB21627E52E5CEB739AF2ECA8CE4660@AM4PR0701MB2162.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=Richard.Earnshaw@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=nd@arm.com \
--cc=ramana.gcc@googlemail.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).