From: H.J. Lu <hjl@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Revert "x86: Don't check if AVX512 template requires AVX512VL"
Date: Thu, 22 Jun 2023 19:38:07 +0000 (GMT) [thread overview]
Message-ID: <20230622193807.4207A3858418@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a61cb9dbc6a8be0922ec5992cf125a5cd389e016
commit a61cb9dbc6a8be0922ec5992cf125a5cd389e016
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Thu Jun 22 12:37:51 2023 -0700
Revert "x86: Don't check if AVX512 template requires AVX512VL"
This reverts commit c7face14225296a2f5d3ebeb8ace88c166d80c3e.
Diff:
---
gas/config/tc-i386.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gas/config/tc-i386.c b/gas/config/tc-i386.c
index dcafac0c0cd..de35ee2a2c6 100644
--- a/gas/config/tc-i386.c
+++ b/gas/config/tc-i386.c
@@ -6288,10 +6288,11 @@ check_VecOperands (const insn_template *t)
/* Templates allowing for ZMMword as well as YMMword and/or XMMword for
any one operand are implicity requiring AVX512VL support if the actual
operand size is YMMword or XMMword. Since this function runs after
- template matching, there's no need to check for YMMword/XMMword nor
- AVX512VL in the template. */
+ template matching, there's no need to check for YMMword/XMMword in
+ the template. */
cpu = cpu_flags_and (t->cpu_flags, avx512);
if (!cpu_flags_all_zero (&cpu)
+ && !t->cpu_flags.bitfield.cpuavx512vl
&& !cpu_arch_flags.bitfield.cpuavx512vl)
{
for (op = 0; op < t->operands; ++op)
reply other threads:[~2023-06-22 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230622193807.4207A3858418@sourceware.org \
--to=hjl@sourceware.org \
--cc=bfd-cvs@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).