From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Set Prefer_No_VZEROUPPER if AVX512ER is available
Date: Mon, 17 Apr 2017 20:13:00 -0000 [thread overview]
Message-ID: <CAMe9rOpW2QAZGKiRMR3OPY=PcGg4ZFB256NiKpWCuWNG1D3meg@mail.gmail.com> (raw)
In-Reply-To: <4f793a5a-d60f-67e8-a100-c1ae2dc8beb2@redhat.com>
On Mon, Apr 17, 2017 at 1:06 PM, Florian Weimer <fweimer@redhat.com> wrote:
> On 04/17/2017 09:54 PM, H.J. Lu wrote:
>>
>> Since AVX512ER is unique to Xeon Phi, set Prefer_No_VZEROUPPER if
>> AVX512ER is available.
>
>
> This approach doesn't seem very future-proof to me.
>
AVX512ER won't be implemented in any Xeon processors and it will be in
all Xeon Phi processors. In this way, we don't need to check CPU model
numbers when setting Prefer_No_VZEROUPPER. It will work with current
and future Xeon Phi and non-Xeon Phi processors.
--
H.J.
next prev parent reply other threads:[~2017-04-17 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 19:54 H.J. Lu
2017-04-17 20:06 ` Florian Weimer
2017-04-17 20:13 ` H.J. Lu [this message]
2017-04-18 5:48 ` 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='CAMe9rOpW2QAZGKiRMR3OPY=PcGg4ZFB256NiKpWCuWNG1D3meg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.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).