This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: Add <sys/platform/x86.h> to glibc 2.29


On Fri, Aug 17, 2018 at 9:19 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 08/17/2018 05:45 PM, H.J. Lu wrote:
>>
>> 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));
>
>
> Sorry, this does not answer my question.

Just like __get_cpu_features, they can be used in IFUNC resolvers.

>>> Shouldn't these identifiers be in the public (non-internal) namespace?
>>>
>>
>> Do we have precedents for such arch specific public functions?
>
>
> There is modify_ldt.
>

Which header file has its prototype?

-- 
H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]