This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: Add <sys/platform/x86.h> to glibc 2.29
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 17 Aug 2018 08:45:49 -0700
- Subject: Re: RFC: Add <sys/platform/x86.h> to glibc 2.29
- References: <20180729161623.GA17944@gmail.com> <ffb5c746-1672-076c-e1e2-ae6c4f435026@redhat.com>
On Fri, Aug 17, 2018 at 7:50 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 07/29/2018 06:16 PM, H.J. Lu wrote:
>>
>> extern enum cpu_features_kind __x86_get_cpu_kind (void)
>> __attribute__ ((const));
>>
>> extern const struct cpuid_registers *__x86_get_cpuid_registers
>> (unsigned int) __attribute__ ((const));
>>
>> extern unsigned int __x86_get_arch_feature (unsigned int)
>> __attribute__ ((const));
>
>
> Are these functions supposed to be usable in IFUNC resolvers?
They have the same limitation as
/* Used from outside of glibc to get access to the CPU features
structure. */
extern const struct cpu_features *__get_cpu_features (void)
__attribute__ ((const));
> Shouldn't these identifiers be in the public (non-internal) namespace?
>
Do we have precedents for such arch specific public functions?
--
H.J.