From: Mark Wielaard <mark@klomp.org>
To: Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, gcc@gcc.gnu.org,
llvm-dev@lists.llvm.org, x86-64-abi@googlegroups.com
Cc: "Mallappa, Premachandra" <Premachandra.Mallappa@amd.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Michael Matz <matz@suse.de>,
Tom Stellard <tstellar@redhat.com>, Jeff Law <law@redhat.com>
Subject: Re: New x86-64 micro-architecture levels
Date: Wed, 15 Jul 2020 16:38:52 +0200 [thread overview]
Message-ID: <ae608575d0b2d70dc8b6c06d49efe94edd4c7350.camel@klomp.org> (raw)
In-Reply-To: <87365zz3a6.fsf@oldenburg2.str.redhat.com>
Hi Florian,
I understand you want to discuss the x86_64 micro-architecture levels
only in this thread, but it would be nice to have a similar discussion
for other architectures.
One thing that wasn't clear to me from this proposal is how the glibc
dynamic loader checks for the CPU feature flags. This is important for
valgrind since it can communicate those through different means. cpuid
interception, auxv AT_HWCAP/AT_HWCAP2 interception (but not AT_PLATFORM
at the moment) and of course we can generate SIGILL for unsupported
instructions. We currently don't intercept /proc/cpuinfo (but could).
I think it is important to be precise here, because in the past this
has sometimes caused confusion. For example for how to check correctly
for avx, lzcnt, or fma[4] support.
Thanks,
Mark
P.S. I don't particular like the numbered names, but well, bike-shed...
next prev parent reply other threads:[~2020-07-15 14:38 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 [this message]
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=ae608575d0b2d70dc8b6c06d49efe94edd4c7350.camel@klomp.org \
--to=mark@klomp.org \
--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).