From: Florian Weimer <fw@deneb.enyo.de>
To: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
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 17:07:21 +0100 [thread overview]
Message-ID: <87d0mmvoee.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <02c15fb3-47e5-1900-c8d9-418c6e942748@arm.com> (Szabolcs Nagy's message of "Tue, 19 Mar 2019 16:03:51 +0000")
* Szabolcs Nagy:
> 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).
It could be a pointer to a struct with the struct size as the first
member. That's really simple and could work on other architectures,
too.
Or we could delay IFUNC resolvers after other relocations, so that
IFUNC resolvers can use arbitrary data symbols from the dynamic loader
because all data relocations have been processed before they run.
Then we won't have to add additional IFUNC resolver arguments ever
again, and can use the regular ABI maintenance to deal with
compatibility issues.
prev parent reply other threads:[~2019-03-19 16:07 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
2019-03-19 16:07 ` Florian Weimer [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
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=87d0mmvoee.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=Szabolcs.Nagy@arm.com \
--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).