This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: PATCH: Check GLIBC_IFUNC to enable/disable ifunc features
- From: Siddhesh Poyarekar <siddhesh at sourceware dot org>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <sid at reserved-bit dot com>, nd at arm dot com
- Date: Thu, 30 Jun 2016 20:13:20 +0530
- Subject: Re: PATCH: Check GLIBC_IFUNC to enable/disable ifunc features
- Authentication-results: sourceware.org; auth=none
- References: <CAMe9rOq1+_rMbs1mt3=Md=Wx=7ZxUbD+BhOx-qrO5TBRBrRLww at mail dot gmail dot com> <20160630013716 dot GY4685 at vapier dot lan> <CAMe9rOrgshV6t5quE01r_oc91ps0JJ7fYfAC=MuQOs96qNv1uQ at mail dot gmail dot com> <57752F1B dot 7010809 at arm dot com>
On Thu, Jun 30, 2016 at 03:39:23PM +0100, Szabolcs Nagy wrote:
> since it is for glibc devs only is it expected to be
> stable across glibc versions?
>
> may be the env var name could reflect that it is not
> a public api.
Maybe this is a use case for a GLIBC_PRIVATE namespace? In any case,
if this is going to be part of tunables, there's no ABI/API guarantee
associated with it. That is, tunables in version may not be present
in another.
Siddhesh