public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Add AArch64 HWCAP2_* constants from Linux 5.19
Date: Mon, 22 Aug 2022 15:55:56 +0100	[thread overview]
Message-ID: <YwOY/LxtXXqk5SlB@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208171755190.417173@digraph.polyomino.org.uk>

The 08/17/2022 17:55, Joseph Myers wrote:
> Linux 5.19 adds more HWCAP2_* values for AArch64; add these to its
> bits/hwcap.h header in glibc.
> 
> Tested with build-many-glibcs.py for aarch64-linux-gnu.

this is ok to commit, thanks.

Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>

> 
> diff --git a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
> index 616239bb84..07cb962a7b 100644
> --- a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
> +++ b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
> @@ -78,3 +78,12 @@
>  #define HWCAP2_AFP		(1 << 20)
>  #define HWCAP2_RPRES		(1 << 21)
>  #define HWCAP2_MTE3		(1 << 22)
> +#define HWCAP2_SME		(1 << 23)
> +#define HWCAP2_SME_I16I64	(1 << 24)
> +#define HWCAP2_SME_F64F64	(1 << 25)
> +#define HWCAP2_SME_I8I32	(1 << 26)
> +#define HWCAP2_SME_F16F32	(1 << 27)
> +#define HWCAP2_SME_B16F32	(1 << 28)
> +#define HWCAP2_SME_F32F32	(1 << 29)
> +#define HWCAP2_SME_FA64		(1 << 30)
> +#define HWCAP2_WFXT		(1UL << 31)
> 
> -- 
> Joseph S. Myers
> joseph@codesourcery.com

      reply	other threads:[~2022-08-22 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 17:55 Joseph Myers
2022-08-22 14:55 ` Szabolcs Nagy [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=YwOY/LxtXXqk5SlB@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).