From: Jan Beulich <jbeulich@suse.com>
To: "Cui,Lili" <lili.cui@intel.com>
Cc: binutils@sourceware.org, hjl.tools@gmail.com
Subject: Re: [PATCH 1/2] [PATCH 1/2] Enable Intel AVX512_FP16 instructions
Date: Fri, 2 Jul 2021 17:46:34 +0200 [thread overview]
Message-ID: <cd65399b-bd9b-3ae7-1084-13d5271da25b@suse.com> (raw)
In-Reply-To: <4a0884b4-87f2-4884-8b64-c9c562452a64@suse.com>
On 02.07.2021 15:42, Jan Beulich via Binutils wrote:
> vcvtph2pd may need to have their AVX512VL templates split: Having
> e.g. Word|RegXMM|Dword means Word is the broadcast form and both
> XmmWord and Dword can be used with non-broadcast memory operands.
> But that's not true - in Intel syntax only "dword ptr" ought to be
> valid there, afaict. Same for vcvtph2qq (where the group also has
> a stray blank line in the middle), vcvtph2uqq, vcvttph2qq, and
> vcvttph2uqq.
Hmm, looking at your testcase addition to xmmword.s I'm guessing
now that I was wrong with the above, albeit I couldn't point at
the code in tc-i386.c that's making this work.
Jan
next prev parent reply other threads:[~2021-07-02 15:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 7:47 [PATCH 0/2]Enable Intel AVX512_FP16 instructions and add tests for it Cui,Lili
2021-07-01 7:47 ` [PATCH 1/2] [PATCH 1/2] Enable Intel AVX512_FP16 instructions Cui,Lili
2021-07-02 13:42 ` Jan Beulich
2021-07-02 15:46 ` Jan Beulich [this message]
2021-07-06 12:42 ` Cui, Lili
2021-07-09 11:52 ` Cui, Lili
2021-07-13 7:25 ` Jan Beulich
2021-07-13 7:35 ` Cui, Lili
2021-07-02 15:08 ` Jan Beulich
2021-07-09 11:50 ` Cui, Lili
2021-07-05 6:30 ` Jan Beulich
2021-07-05 12:38 ` H.J. Lu
2021-07-06 12:48 ` Cui, Lili
2021-07-09 11:47 ` Cui, Lili
2021-07-09 12:16 ` Jan Beulich
2021-07-13 6:58 ` Cui, Lili
2021-07-13 7:54 ` Jan Beulich
2021-07-13 8:03 ` Cui, Lili
2021-07-13 16:25 ` Jan Beulich
[not found] ` <DM6PR11MB4009305D09B37299FC2F282C9EE39@DM6PR11MB4009.namprd11.prod.outlook.com>
2021-07-21 14:29 ` Jan Beulich
2021-07-22 7:05 ` Cui, Lili
2021-07-14 15:21 ` Jan Beulich
2021-07-20 7:08 ` FW: " Cui, Lili
2021-07-20 8:46 ` Jan Beulich
2021-07-20 11:13 ` Cui, Lili
2021-07-20 11:26 ` Cui, Lili
2021-07-20 13:02 ` Jan Beulich
2021-07-20 13:38 ` Cui, Lili
2021-07-20 14:15 ` Jan Beulich
2021-07-20 14:29 ` Cui, Lili
2021-07-21 10:32 ` Jan Beulich
2021-07-01 15:42 ` [PATCH 0/2]Enable Intel AVX512_FP16 instructions and add tests for it H.J. Lu
2021-07-01 17:46 ` H.J. Lu
2021-07-02 0:13 ` Cui, Lili
[not found] ` <20210701074736.9534-3-lili.cui@intel.com>
2021-07-02 15:44 ` [PATCH 2/2] [PATCH 2/2] Add tests for Intel AVX512_FP16 instructions Jan Beulich
[not found] ` <BY5PR11MB4008FDC77679D0F8FB9E88B39E149@BY5PR11MB4008.namprd11.prod.outlook.com>
2021-07-13 15:59 ` Jan Beulich
2021-07-14 18:01 ` H.J. Lu
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=cd65399b-bd9b-3ae7-1084-13d5271da25b@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=lili.cui@intel.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).