From: Richard Biener <richard.guenther@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GCC Development <gcc@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
Tom Stellard <tstellar@redhat.com>,
llvm-dev@lists.llvm.org, "Mallappa,
Premachandra" <Premachandra.Mallappa@amd.com>,
x86-64-abi <x86-64-abi@googlegroups.com>
Subject: Re: New x86-64 micro-architecture levels
Date: Mon, 13 Jul 2020 10:57:26 +0200 [thread overview]
Message-ID: <CAFiYyc2t4_A7MrxAPBwgrSc405GniV6Xgwpisjn4ibh=qLudZA@mail.gmail.com> (raw)
In-Reply-To: <87pn8zuaky.fsf@oldenburg2.str.redhat.com>
On Mon, Jul 13, 2020 at 9:40 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Richard Biener:
>
> >> Looks good. I like it.
> >
> > Likewise. Btw, did you check that VIA family chips slot into Level A
> > at least?
>
> Those seem to lack SSE4.2, so they land in the baseline.
>
> > Where do AMD bdverN slot in?
>
> bdver1 to bdver3 (as defined by GCC) should land in Level B (so Level A
> if that is dropped). bdver4 and znver1 (and later) should land in
> Level C.
>
> >> My only concerns are
> >>
> >> 1. Names like “x86-100”, “x86-101”, what features do they support?
> >
> > Indeed I didn't get the -100, -101 part. On the GCC side I'd have
> > suggested -march=generic-{A,B,C,D} implying the respective
> > -mtune.
>
> With literal A, B, C, D, or are they just placeholders? If not literal
> levels, then what we should use there?
>
> I like the simplicity of numbers. I used letters in the proposal to
> avoid confusion if we alter the proposal by dropping or levels, shifting
> the meaning of those that come later. I expect to switch back to
> numbers again for the final version.
They are indeed placeholders though I somehow prefer letters to
numbers. But this is really bike-shedding territory. Good documentation
on the tools side will be more imporant as well as consistent spelling
between tools sets, possibly driven by a good choice from within the
psABI document.
Richard.
next prev parent reply other threads:[~2020-07-13 8:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 17:30 Florian Weimer
2020-07-10 19:14 ` Joseph Myers
2020-07-13 7:55 ` Florian Weimer
2020-07-10 21:42 ` H.J. Lu
2020-07-13 6:23 ` Richard Biener
2020-07-13 7:40 ` Florian Weimer
2020-07-13 7:47 ` Jan Beulich
2020-07-13 13:31 ` H.J. Lu
2020-07-13 13:53 ` Jakub Jelinek
2020-07-13 8:57 ` Richard Biener [this message]
2020-07-13 6:49 ` Florian Weimer
2020-07-13 13:30 ` H.J. Lu
2020-07-11 7:40 ` Allan Sandfeld Jensen
2020-07-13 6:58 ` Florian Weimer
2020-07-15 14:38 ` Mark Wielaard
2020-07-15 14:45 ` H.J. Lu
2020-07-15 14:56 ` Florian Weimer
2020-07-21 16:05 ` Mallappa, Premachandra
2020-07-21 18:04 ` Florian Weimer
2020-07-22 1:31 ` Dongsheng Song
2020-07-22 8:44 ` Florian Weimer
2020-07-22 9:26 ` Richard Biener
2020-07-22 10:16 ` Florian Weimer
2020-07-22 13:50 ` Richard Biener
2020-07-22 14:21 ` H.J. Lu
2020-07-31 13:06 ` Carlos O'Donell
2020-07-22 7:48 ` Jan Beulich
2020-07-22 10:34 ` Florian Weimer
2020-07-22 11:41 ` Jan Beulich
2020-07-31 13:20 ` Carlos O'Donell
2020-07-22 16:45 ` Mallappa, Premachandra
2020-07-23 12:44 ` Michael Matz
2020-07-23 13:21 ` H.J. Lu
2020-07-28 15:54 ` Florian Weimer
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='CAFiYyc2t4_A7MrxAPBwgrSc405GniV6Xgwpisjn4ibh=qLudZA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=Premachandra.Mallappa@amd.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.org \
--cc=tstellar@redhat.com \
--cc=x86-64-abi@googlegroups.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).