From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Andrea Corallo <Andrea.Corallo@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Andrea Corallo <Andrea.Corallo@arm.com>
Subject: RE: [PATCH] arm: Define __ARM_FEATURE_AES and __ARM_FEATURE_SHA2 when march +crypto is selected
Date: Wed, 28 Sep 2022 12:23:05 +0000 [thread overview]
Message-ID: <PAXPR08MB692626C977EA75FFF657701993549@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20220928121926.13280-1-andrea.corallo@arm.com>
Hi Andrea,
> -----Original Message-----
> From: Andrea Corallo <andrea.corallo@arm.com>
> Sent: Wednesday, September 28, 2022 1:19 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>; Richard Earnshaw
> <Richard.Earnshaw@arm.com>; Andrea Corallo <Andrea.Corallo@arm.com>
> Subject: [PATCH] arm: Define __ARM_FEATURE_AES and
> __ARM_FEATURE_SHA2 when march +crypto is selected
>
> Hi all,
>
> this patch fixes the missing definition of __ARM_FEATURE_AES and
> __ARM_FEATURE_SHA2 when AES SHA1 & SHA2 crypto instructions are
> available [1] (read when march +crypto is selected).
>
> Okay for master?
Ok.
Thanks,
Kyrill
>
> Thanks
>
> Andrea
>
> [1] <https://raw.githubusercontent.com/ARM-
> software/acle/main/main/acle.md>
>
> /gcc/ChangeLog
>
> 2022-09-14 Andrea Corallo <andrea.corallo@arm.com>
>
> * config/arm/arm-c.cc (arm_cpu_builtins): Define
> __ARM_FEATURE_AES and __ARM_FEATURE_SHA2.
>
> gcc/testsuite/ChangeLog
>
> 2022-09-14 Andrea Corallo <andrea.corallo@arm.com>
>
> * gcc.target/arm/attr-crypto.c: Update test.
> ---
> gcc/config/arm/arm-c.cc | 2 ++
> gcc/testsuite/gcc.target/arm/attr-crypto.c | 8 ++++++++
> 2 files changed, 10 insertions(+)
>
> diff --git a/gcc/config/arm/arm-c.cc b/gcc/config/arm/arm-c.cc
> index a8697b8c62f..86c56bf2680 100644
> --- a/gcc/config/arm/arm-c.cc
> +++ b/gcc/config/arm/arm-c.cc
> @@ -202,6 +202,8 @@ arm_cpu_builtins (struct cpp_reader* pfile)
> def_or_undef_macro (pfile, "__ARM_FEATURE_QBIT",
> TARGET_ARM_QBIT);
> def_or_undef_macro (pfile, "__ARM_FEATURE_SAT", TARGET_ARM_SAT);
> def_or_undef_macro (pfile, "__ARM_FEATURE_CRYPTO",
> TARGET_CRYPTO);
> + def_or_undef_macro (pfile, "__ARM_FEATURE_AES", TARGET_CRYPTO);
> + def_or_undef_macro (pfile, "__ARM_FEATURE_SHA2", TARGET_CRYPTO);
>
> def_or_undef_macro (pfile, "__ARM_FEATURE_UNALIGNED",
> unaligned_access);
>
> diff --git a/gcc/testsuite/gcc.target/arm/attr-crypto.c
> b/gcc/testsuite/gcc.target/arm/attr-crypto.c
> index cbd13a757d8..05e458f36b6 100644
> --- a/gcc/testsuite/gcc.target/arm/attr-crypto.c
> +++ b/gcc/testsuite/gcc.target/arm/attr-crypto.c
> @@ -16,6 +16,14 @@
> #error __ARM_FEATURE_CRYPTO not defined.
> #endif
>
> +#ifndef __ARM_FEATURE_AES
> +#error __ARM_FEATURE_AES not defined.
> +#endif
> +
> +#ifndef __ARM_FEATURE_SHA2
> +#error __ARM_FEATURE_SHA2 not defined.
> +#endif
> +
> #ifndef __ARM_NEON
> #error __ARM_NEON not defined.
> #endif
> --
> 2.25.1
next prev parent reply other threads:[~2022-09-28 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:19 Andrea Corallo
2022-09-28 12:23 ` Kyrylo Tkachov [this message]
2022-09-28 13:26 ` Andrea Corallo
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=PAXPR08MB692626C977EA75FFF657701993549@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Andrea.Corallo@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.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).