From: Jan Beulich <jbeulich@suse.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Mallappa, Premachandra" <Premachandra.Mallappa@amd.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"llvm-dev@lists.llvm.org" <llvm-dev@lists.llvm.org>,
"x86-64-abi@googlegroups.com" <x86-64-abi@googlegroups.com>,
"H.J. Lu" <hjl.tools@gmail.com>, "matz@suse.de" <matz@suse.de>,
Tom Stellard <tstellar@redhat.com>, Jeff Law <law@redhat.com>
Subject: Re: New x86-64 micro-architecture levels
Date: Wed, 22 Jul 2020 13:41:18 +0200 [thread overview]
Message-ID: <8144f593-1a0d-9b5d-094c-fc44021531d3@suse.com> (raw)
In-Reply-To: <87y2nbj0st.fsf@oldenburg2.str.redhat.com>
On 22.07.2020 12:34, Florian Weimer wrote:
> The remaining issue is the - vs _ issue. I think GCC currently uses
> “x86-64” in places that are not part of identifiers or target triplets.
> Richard mentioned “x86_64-” as a potential choice. Would it be too
> awkward to have ”-march=x86_64-…”?
Personally I'm advocating for avoiding underscores whenever dashes
can also be used, and whenever they're not needed to distinguish
themselves from dashes (like in target triplets). But this doesn't
make their use "awkward" here of course - it's just my personal
view on it. And maybe, despite the main was sent _to_ just me, it
was really me you meant to ask ...
Jan
next prev parent reply other threads:[~2020-07-22 11:41 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
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 [this message]
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=8144f593-1a0d-9b5d-094c-fc44021531d3@suse.com \
--to=jbeulich@suse.com \
--cc=Premachandra.Mallappa@amd.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=law@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.org \
--cc=matz@suse.de \
--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).