This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH][aarch64] Fix hpwcap argument passed to ifunc resolvers
- From: Steve Ellcey <sellcey at cavium dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Cc: nd at arm dot com
- Date: Thu, 31 Aug 2017 09:12:06 -0700
- Subject: Re: [PATCH][aarch64] Fix hpwcap argument passed to ifunc resolvers
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve dot Ellcey at cavium dot com;
- References: <email@example.com> <59A8291E.firstname.lastname@example.org>
- Reply-to: sellcey at cavium dot com
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On Thu, 2017-08-31 at 16:19 +0100, Szabolcs Nagy wrote:
> i'm not yet convinced that LD_HWCAP_MASK should be
> applied to ifunc resolvers: glibc might be interested
> in different hwcap flags than external users and the
> important hwcaps mask has other effect in glibc that
> i need to review.
Personally, I like the idea that LD_HWCAP_MASK can affect ifunc
resolvers. It gives users a single method to turn off some hardware
capability across all libraries. I can see where finer grain control
might also be useful but I think that in general we are going to have
situations where a particular hardware capability is just not working
the way it should and so we want to turn off its use everywhere in an
> please do the type change and the masking in separate
> patches (the libatomic change should work without masking
> it's just not possible to opt out using an envvar).
OK, I have sent this off in a seperate thread.