From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Christophe Lyon <christophe.lyon@linaro.org>
Cc: Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>, nd <nd@arm.com>
Subject: Re: [PING**2] [PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
Date: Tue, 05 Sep 2017 17:53:00 -0000 [thread overview]
Message-ID: <59AEE480.5070909@foss.arm.com> (raw)
In-Reply-To: <AM5PR0701MB2657051ED4B09B4EF3E5E59BE4960@AM5PR0701MB2657.eurprd07.prod.outlook.com>
On 05/09/17 18:48, Bernd Edlinger wrote:
> On 09/05/17 17:02, Wilco Dijkstra wrote:
>> Bernd Edlinger wrote:
>>
>>> Combine creates an invalid insn out of these two insns:
>> Yes it looks like a latent bug. We need to use arm_general_register_operand
>> as arm_adddi3/subdi3 only allow integer registers. You don't need a new predicate
>> s_register_operand_nv. Also I'd prefer something like arm_general_adddi_operand.
>>
> Thanks, attached is a patch following your suggestion.
>
>> + "TARGET_32BIT && ((!TARGET_NEON && !TARGET_IWMMXT) || reload_completed)"
>>
>> The split condition for adddi3 now looks more accurate indeed, although we could
>> remove the !TARGET_NEON from the split condition as this is always true given
>> arm_adddi3 uses "TARGET_32BIT && !TARGET_NEON".
>>
> No, the split condition does not begin with "&& TARGET_32BIT...".
> Therefore the split is enabled in TARGET_NEON after reload_completed.
> And it is invoked from adddi3_neon for all alternatives without vfp
> registers:
>
> switch (which_alternative)
> {
> case 0: /* fall through */
> case 3: return "vadd.i64\t%P0, %P1, %P2";
> case 1: return "#";
> case 2: return "#";
> case 4: return "#";
> case 5: return "#";
> case 6: return "#";
>
>
>
>> Also there are more cases, a quick grep suggests *anddi_notdi_di has the same issue.
>>
> Yes, that pattern can be cleaned up in a follow-up patch.
> Note this splitter is invoked from bicdi3_neon as well.
> However I think anddi_notdi_di should be safe as long as it is enabled
> after reload_completed (which is probably a bug).
>
Thanks, that's what I had in mind in my other reply.
This is ok if testing comes back ok.
Kyrill
> Bernd.
>
>> Wilco
>>
next prev parent reply other threads:[~2017-09-05 17:53 UTC|newest]
Thread overview: 28+ 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
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 [this message]
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
2016-11-16 17:28 [PING] " Bernd Edlinger
2016-11-24 14:24 ` [PING**2] " Bernd Edlinger
2016-12-05 13:41 ` [PING] " Bernd Edlinger
2016-12-12 5:59 ` [PING**2] " Bernd Edlinger
2016-12-19 8:22 ` Bernd Edlinger
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=59AEE480.5070909@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=bernd.edlinger@hotmail.de \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--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).