This is the mail archive of the
mailing list for the GCC project.
Re: [patch2/2][arm]: remove builtin expand for sha1
- From: Kyrill Tkachov <kyrylo dot tkachov at foss dot arm dot com>
- To: Sylvia Taylor <Sylvia dot Taylor at arm dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>, Ramana Radhakrishnan <Ramana dot Radhakrishnan at arm dot com>
- Cc: nd <nd at arm dot com>
- Date: Thu, 18 Jul 2019 17:04:08 +0100
- Subject: Re: [patch2/2][arm]: remove builtin expand for sha1
- References: <AM6PR08MB3559F4AEBF0DCA9588E389B3E0FB0@AM6PR08MB3559.eurprd08.prod.outlook.com>
On 7/3/19 10:36 AM, Sylvia Taylor wrote:
This patch removes the builtin expand handling for sha1h/c/m/p and
replaces it with expand patterns. This should make it more consistent
with how we handle intrinsic implementations and cleans up the custom
sha1 code in the arm_expand builtins for unop and ternop.
Bootstrapped and tested on arm-none-linux-gnueabihf.
2019-07-03 Sylvia Taylor <email@example.com>
(arm_expand_ternop_builtin): Remove builtin_sha1cpm.
(arm_expand_unop_builtin): Remove builtin_sha1h.
(crypto_sha1h): New expand pattern.
This doesn't exactly match what the patch looks. You don't need to list
the names the iterators expand into.
We just need the string of the names as it appears in the MD files.
Granted, this is a tricky case for ChangeLog writing as
define_insns are converted to define_expand, things are renamed etc...
I've taken the liberty of updating the ChangeLog to:
2019-07-18 Sylvia Taylor <firstname.lastname@example.org>
(arm_expand_ternop_builtin): Remove explicit sha1 builtin handling.
(crypto_sha1h): Convert from define_insn to define_expand.
(crypto_sha1h_lb): New define_insn.
and committed as r273575.
Thanks for the nice cleanup!