public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Add AArch64 HWCAP2_EBF16 from Linux 6.0 to bits/hwcap.h Date: Wed, 12 Oct 2022 14:28:28 +0000 (GMT) [thread overview] Message-ID: <20221012142828.63D5B3895FFF@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3bd18aa4d1d4c3d34d7033de3f3920cddab90008 commit 3bd18aa4d1d4c3d34d7033de3f3920cddab90008 Author: Joseph Myers <joseph@codesourcery.com> Date: Wed Oct 12 14:28:14 2022 +0000 Add AArch64 HWCAP2_EBF16 from Linux 6.0 to bits/hwcap.h Linux 6.0 adds a new AArch64 HWCAP2 bit, HWCAP2_EBF16. Add this to glibc's bits/hwcap.h. Tested with build-many-glibcs.py for aarch64-linux-gnu. Diff: --- sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h | 1 + 1 file changed, 1 insertion(+) diff --git a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h index 07cb962a7b..25a220525e 100644 --- a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h +++ b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h @@ -87,3 +87,4 @@ #define HWCAP2_SME_F32F32 (1 << 29) #define HWCAP2_SME_FA64 (1 << 30) #define HWCAP2_WFXT (1UL << 31) +#define HWCAP2_EBF16 (1UL << 32)
reply other threads:[~2022-10-12 14:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221012142828.63D5B3895FFF@sourceware.org \ --to=jsm28@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).