This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: IFUNC resolvers for non-function symbols
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Cc: <nd at arm dot com>
- Date: Tue, 24 Jan 2017 13:55:24 +0000
- Subject: Re: IFUNC resolvers for non-function symbols
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Szabolcs dot Nagy at arm dot com;
- Nodisclaimer: True
- References: <3e0801af-194a-6890-df75-1708ed3298b2@redhat.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 24/01/17 12:46, Florian Weimer wrote:
> To which extent do we need to support IFUNC resolvers which are used by non-function relocations?
>
> For example, do we need to support copy relocations where the object address is determined by an IFUNC resolver?
>
> The x86-64 psABI, for example, does not seem to be very explicit what the expected scope of support is.
the ifunc spec i know about
https://sites.google.com/site/x32abi/documents
says
STT_GNU_IFUNC
This symbol type is the same as STT_FUNC except that it always
points to a function or piece of executable code which takes no
arguments and returns a function pointer. [..]
this implies to me that ifunc resolver is not applicable to data.