From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: V4: [PATCH] x86: Install <sys/platform/x86.h> [BZ #26124]
Date: Wed, 24 Jun 2020 14:10:19 -0700 [thread overview]
Message-ID: <CAMe9rOokWC_NrHEBQB43zxyLPRGHgdqb+w1=7oHGuhmnPi43Qw@mail.gmail.com> (raw)
In-Reply-To: <697cab8a-2d75-ef36-9e09-dbfe6daa4ae1@linaro.org>
On Wed, Jun 24, 2020 at 1:04 PM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
>
>
> On 24/06/2020 11:33, Florian Weimer via Libc-alpha wrote:
> > * H. J. Lu:
> >
> >> Here is the updated patch with
> >>
> >> -- Macro: int HAS_CPU_FEATURE (NAME)
> >> This macro returns a nonzero value (true) if the processor has the
> >> feature NAME.
> >>
> >> -- Macro: int CPU_FEATURE_USABLE (NAME)
> >> This macro returns a nonzero value (true) if the processor has the
> >> feature NAME and the feature is supported by the operating system.
> >
> > This is indeed less confusing. Thanks.
> >
> > I'm still convinced we have a real use case for HAS_CPU_FEATURE.
> >
> > Does anyone else want to comment on this?
> >
> > Thanks,
> > Florian
> >
>
> Should we provide it only for __USE_GNU (_GNU_SOURCE)? And I guess that cpuid
Do we do that for other <sys/platform/XXX.h> files?
> is not expected to be extendable. The macro API is not my favorite way of
We can expand the cpuid array. We just need to add an alias to
__x86_get_cpu_features
with a new symbol version.
> doing it, but it looks ok.
I will check it in tomorrow if there are no further comments.
Thanks.
--
H.J.
next prev parent reply other threads:[~2020-06-24 21:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:31 [PATCH] x86: Install <cpu-features.h> " H.J. Lu
2020-06-17 20:54 ` Joseph Myers
2020-06-18 0:08 ` [PATCH] x86: Install <sys/platform/x86.h> " H.J. Lu
2020-06-18 8:45 ` Florian Weimer
2020-06-18 16:14 ` V2: " H.J. Lu
2020-06-22 9:09 ` Florian Weimer
2020-06-22 20:25 ` V3: " H.J. Lu
2020-06-22 20:41 ` Florian Weimer
2020-06-22 20:53 ` H.J. Lu
2020-06-22 21:14 ` Florian Weimer
2020-06-22 22:18 ` H.J. Lu
2020-06-22 23:14 ` V4: " H.J. Lu
2020-06-24 14:33 ` Florian Weimer
2020-06-24 20:04 ` Adhemerval Zanella
2020-06-24 21:10 ` H.J. Lu [this message]
2020-06-25 7:33 ` Florian Weimer
2020-06-25 12:30 ` V5: " H.J. Lu
2020-06-25 13:20 ` V6: " H.J. Lu
2020-06-26 12:52 ` H.J. Lu
2020-06-26 13:20 ` Florian Weimer
2020-06-26 13:44 ` H.J. Lu
2020-06-29 16:13 ` Florian Weimer
2020-06-29 16:44 ` H.J. Lu
2020-06-29 16:49 ` Florian Weimer
2020-06-30 0:29 ` H.J. Lu
2020-06-30 9:46 ` Florian Weimer
2020-06-30 12:19 ` H.J. Lu
2020-06-24 22:07 ` V4: " Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOokWC_NrHEBQB43zxyLPRGHgdqb+w1=7oHGuhmnPi43Qw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).