unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@redhat.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: PING^3: V8 [PATCH 2/2] x86: Install <sys/platform/x86.h> [BZ #26124]
Date: Wed, 2 Sep 2020 05:55:43 -0700	[thread overview]
Message-ID: <CAMe9rOrrNJkNKVu5xk5ESkehT9WU4NDE_AYZZxxoEmp5u+Z09Q@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOq03C9-DWpKC8tf2GvXov_K0hut874o6b=NH_+6HBgxEw@mail.gmail.com>

On Wed, Aug 19, 2020 at 5:52 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Wed, Aug 12, 2020 at 7:00 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Wed, Aug 5, 2020 at 4:01 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >
> > > Install <sys/platform/x86.h> so that programmers can do
> > >
> > >  #if __has_include(<sys/platform/x86.h>)
> > >  #include <sys/platform/x86.h>
> > >  #endif
> > >  ...
> > >
> > >    if (CPU_FEATURE_USABLE (SSE2))
> > >  ...
> > >    if (CPU_FEATURE_USABLE (AVX2))
> > >  ...
> > >
> > > <sys/platform/x86.h> exports only:
> > >
> > > enum
> > > {
> > >   COMMON_CPUID_INDEX_1 = 0,
> > >   COMMON_CPUID_INDEX_7,
> > >   COMMON_CPUID_INDEX_80000001,
> > >   COMMON_CPUID_INDEX_D_ECX_1,
> > >   COMMON_CPUID_INDEX_80000007,
> > >   COMMON_CPUID_INDEX_80000008,
> > >   COMMON_CPUID_INDEX_7_ECX_1,
> > >   /* Keep the following line at the end.  */
> > >   COMMON_CPUID_INDEX_MAX
> > > };
> > >
> > > struct cpuid_features
> > > {
> > >   struct cpuid_registers cpuid;
> > >   struct cpuid_registers usable;
> > > };
> > >
> > > struct cpu_features
> > > {
> > >   struct cpu_features_basic basic;
> > >   struct cpuid_features features[COMMON_CPUID_INDEX_MAX];
> > > };
> > >
> > > /* Get a pointer to the CPU features structure.  */
> > > extern const struct cpu_features *__x86_get_cpu_features
> > >   (unsigned int max) __attribute__ ((const));
> > >
> > > Since all feature checks are done through macros, programs compiled with
> > > a newer <sys/platform/x86.h> are compatible with the older glibc binaries
> > > as long as the layout of struct cpu_features is identical.  The features
> > > array can be expanded with backward binary compatibility for both .o and
> > > .so files.  When COMMON_CPUID_INDEX_MAX is increased to support new
> > > processor features, __x86_get_cpu_features in the older glibc binaries
> > > returns NULL and HAS_CPU_FEATURE/CPU_FEATURE_USABLE return false on the
> > > new processor feature.  No new symbol version is neeeded.
> > >
> > > Both CPU_FEATURE_USABLE and HAS_CPU_FEATURE are provided.  HAS_CPU_FEATURE
> > > can be used to identify processor features.
> > >
> > > Note: Although GCC has __builtin_cpu_supports, it only supports a subset
> > > of <sys/platform/x86.h> and it is equivalent to CPU_FEATURE_USABLE.  It
> > > doesn't support HAS_CPU_FEATURE.
>
> PING:
>
> https://sourceware.org/pipermail/libc-alpha/2020-August/116865.html
>

If there are no more comments, I will check it next Friday,
Sept 11.


-- 
H.J.

  reply	other threads:[~2020-09-02 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 23:01 V8 [PATCH 1/2] x86: Clear some CPU usable feature bits H.J. Lu via Libc-alpha
2020-08-05 23:01 ` V8 [PATCH 2/2] x86: Install <sys/platform/x86.h> [BZ #26124] H.J. Lu via Libc-alpha
2020-08-12 14:00   ` PING: " H.J. Lu via Libc-alpha
2020-08-19 12:52     ` PING^2: " H.J. Lu via Libc-alpha
2020-09-02 12:55       ` H.J. Lu via Libc-alpha [this message]
2020-09-07 18:21         ` PING^3: " H.J. Lu via Libc-alpha
2020-09-10 14:29           ` H.J. Lu via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMe9rOrrNJkNKVu5xk5ESkehT9WU4NDE_AYZZxxoEmp5u+Z09Q@mail.gmail.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    /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).