public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: [PATCH v2] x86: Add comment with ISA level for all targets support by GCC12.1
Date: Fri, 24 Jun 2022 10:02:38 -0700	[thread overview]
Message-ID: <CAMe9rOq_-RzFM9vOoKHOgM+9jrGpHa09OfXr3--oXaC9M4VkOQ@mail.gmail.com> (raw)
In-Reply-To: <20220624164216.2129400-5-goldstein.w.n@gmail.com>

On Fri, Jun 24, 2022 at 9:42 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
> This is just a quality of life change to make it easier to see how the
> ISA level will effect a given build.
> ---
>  sysdeps/x86/isa-level.h | 67 +++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 65 insertions(+), 2 deletions(-)
>
> diff --git a/sysdeps/x86/isa-level.h b/sysdeps/x86/isa-level.h
> index e1a30ed83e..f14ae5cc00 100644
> --- a/sysdeps/x86/isa-level.h
> +++ b/sysdeps/x86/isa-level.h
> @@ -64,8 +64,71 @@
>  #define MINIMUM_X86_ISA_LEVEL                                                 \
>    (__X86_ISA_V1 + __X86_ISA_V2 + __X86_ISA_V3 + __X86_ISA_V4)
>
> -
> -/*
> +/* ISA levels for known GCC targets as of GCC12.1:
> + *
> + * amdfam10       -> 1
> + * athlon-fx      -> 1
> + * athlon64       -> 1
> + * athlon64-sse3  -> 1
> + * atom           -> 1
> + * barcelona      -> 1
> + * bonnell        -> 1
> + * btver1         -> 1
> + * core2          -> 1
> + * eden-x2        -> 1
> + * eden-x4        -> 1
> + * k8             -> 1
> + * k8-sse3        -> 1
> + * nano           -> 1
> + * nano-1000      -> 1
> + * nano-2000      -> 1
> + * nano-3000      -> 1
> + * nano-x2        -> 1
> + * nano-x4        -> 1
> + * nocona         -> 1
> + * opteron        -> 1
> + * opteron-sse3   -> 1
> + * x86-64         -> 1
> + * bdver1         -> 2
> + * bdver2         -> 2
> + * bdver3         -> 2
> + * btver2         -> 2
> + * core-avx-i     -> 2
> + * corei7         -> 2
> + * corei7-avx     -> 2
> + * goldmont       -> 2
> + * goldmont-plus  -> 2
> + * ivybridge      -> 2
> + * nehalem        -> 2
> + * sandybridge    -> 2
> + * silvermont     -> 2
> + * slm            -> 2
> + * tremont        -> 2
> + * westmere       -> 2
> + * x86-64-v2      -> 2
> + * alderlake      -> 3
> + * bdver4         -> 3
> + * broadwell      -> 3
> + * core-avx2      -> 3
> + * haswell        -> 3
> + * knl            -> 3
> + * knm            -> 3
> + * skylake        -> 3
> + * x86-64-v3      -> 3
> + * znver1         -> 3
> + * znver2         -> 3
> + * znver3         -> 3
> + * cannonlake     -> 4
> + * cascadelake    -> 4
> + * cooperlake     -> 4
> + * icelake-client -> 4
> + * icelake-server -> 4
> + * rocketlake     -> 4
> + * sapphirerapids -> 4
> + * skylake-avx512 -> 4
> + * tigerlake      -> 4
> + * x86-64-v4      -> 4
> + *
>   * CPU Features that are hard coded as enabled/disabled depending on
>   * ISA build level.
>   *    - Values > 0 features are always ENABLED if:
> --
> 2.34.1
>

I don't think it is needed.

-- 
H.J.

  reply	other threads:[~2022-06-24 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:42 [PATCH v2] x86: Align entry for memrchr to 64-bytes Noah Goldstein
2022-06-24 16:42 ` [PATCH v2] x86: Rename strstr_sse2 to strstr_generic as it uses string/strstr.c Noah Goldstein
2022-06-24 17:06   ` H.J. Lu
2022-06-24 16:42 ` [PATCH v2] x86: Remove unused file wmemcmp-sse4 Noah Goldstein
2022-06-24 17:03   ` H.J. Lu
2022-06-24 16:42 ` [PATCH v2] x86: Put wcs{n}len-sse4.1 in the sse4.1 text section Noah Goldstein
2022-06-24 17:05   ` H.J. Lu
2022-07-14  3:02     ` Sunil Pandey
2022-06-24 16:42 ` [PATCH v2] x86: Add comment with ISA level for all targets support by GCC12.1 Noah Goldstein
2022-06-24 17:02   ` H.J. Lu [this message]
2022-06-24 17:15 ` [PATCH v2] x86: Align entry for memrchr to 64-bytes H.J. Lu
2022-07-14  2:59   ` Sunil Pandey

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=CAMe9rOq_-RzFM9vOoKHOgM+9jrGpHa09OfXr3--oXaC9M4VkOQ@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=goldstein.w.n@gmail.com \
    --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).