This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: IFUNCs in libpthread
- From: Florian Weimer <fweimer at redhat dot com>
- To: Steve Ellcey <sellcey at cavium dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 18 May 2017 20:47:56 +0200
- Subject: Re: IFUNCs in libpthread
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 8EDB061D02
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 8EDB061D02
- References: <1495131878.2272.57.camel@cavium.com>
On 05/18/2017 08:24 PM, Steve Ellcey wrote:
> I have a question about multiarch directories and IFUNC. I am
> looking at the possibility of making pthread_spin_lock an IFUNC
> on aarch64 so that there can be a version using LSE instructions
> if they are available. Right now, the only IFUNC's are in libc,
> so having one in libpthread would be a new situation.
We already have IFUNCs in libpthread for forwarding to the libc
implementations, to avoid a linker error, code duplication, and in the
case of vfork, semantic problems.
> I am trying to decide if the multiarch routines should be in
> sysdeps/aarch64/multiarch (where libc multiarch files go and
> where I would like to put my memcpy/memmove IFUNCs), or if
> I should create a sysdeps/aarch64/multiarch/nptl directory or
> perhaps a sysdeps/aarch64/nptl/multiarch directory.
I don't think the separate directory is strictly required.
Thanks,
Florian