From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: nd <nd@arm.com>, Joseph Myers <joseph@codesourcery.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Add AArch64 HWCAPs from Linux 5.0
Date: Tue, 19 Mar 2019 16:03:51 +0000 [thread overview]
Message-ID: <02c15fb3-47e5-1900-c8d9-418c6e942748@arm.com> (raw)
In-Reply-To: <87bm27x79r.fsf@mid.deneb.enyo.de>
On 19/03/2019 14:34, Florian Weimer wrote:
> * Szabolcs Nagy:
>
>>> diff --git a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
>>> b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
>>> index 9a395c597f..5f50623953 100644
>>> --- a/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
>>> +++ b/sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h
>>> @@ -51,3 +51,6 @@
>>> #define HWCAP_ILRCPC (1 << 26)
>>> #define HWCAP_FLAGM (1 << 27)
>>> #define HWCAP_SSBS (1 << 28)
>>> +#define HWCAP_SB (1 << 29)
>>> +#define HWCAP_PACA (1 << 30)
>>> +#define HWCAP_PACG (1UL << 31)
>>
>> Note: we ran out of 32bit hwcaps, so further flags here
>> would not be compatible with ilp32 auxv.
>>
>> the plan is to introduce hwcap2 and keep adding flags
>> there, however that will require a change in ifunc
>> resolver abi if we want to pass down hwcap2.
>> i will try to come up with a fix for that in this
>> release cycle.
>
> Yuck. The last bit should have been used for indicating that
> additional IFUNC resolver information is available. 8-(
the ilp32 port passes uint64_t hwcap to the resolver currently
so the top 32bit can be used by glibc to signal the presence
of additional arguments to the resolver (this should work for
both lp64 and ilp32) however i havent worked out yet what
the additional argument should be (so it's extensible reasonably
in the future).
>
> Is there still a way to fix this without requiring additional ABI
> symbols?
>
next prev parent reply other threads:[~2019-03-19 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 21:30 Add AArch64 HWCAPs from Linux 5.0 Joseph Myers
2019-03-19 9:51 ` Szabolcs Nagy
2019-03-19 14:34 ` Florian Weimer
2019-03-19 16:03 ` Szabolcs Nagy [this message]
2019-03-19 16:07 ` Florian Weimer
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02c15fb3-47e5-1900-c8d9-418c6e942748@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=fw@deneb.enyo.de \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).