From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>, Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: RE: [PATCH v2 2/4] x86/APX: extend SSE2AVX coverage
Date: Thu, 25 Apr 2024 06:09:34 +0000 [thread overview]
Message-ID: <SJ0PR11MB560046F8FD5CE0817BF848529E172@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1f66d44d-4185-48d8-ac74-edb92d372757@suse.com>
> Legacy encoded SIMD insns are converted to AVX ones in that mode. When
> eGPR-s are in use, i.e. with APX, convert to AVX10 insns (where
> available; there are quite a few which can't be converted).
>
> Note that LDDQU is represented as VMOVDQU32 (and the prior use of the
> sse3 template there needs dropping, to get the order right).
>
> Note further that in a few cases, due to the use of templates, AVX512VL
> is used when AVX512F would suffice. Since AVX10 is the main reference,
> this shouldn't be too much of a problem.
> ---
> To preempt the question: If we weren't to do this (i.e. leave legacy-
> encoded SIMD insns using eGPR-s alone), I'd raise the counter question
> of why these insns are supported by APX then in the first place.
>
> By using a mask register (which supposedly shouldn't be used by legacy
> SIMD code) we could likely convert further insns (by emitting a pair of
> replacement ones).
Do you mean you want to allow adding "Masking" to legacy SIMD code? Like you did with Disp8MemShift?
> ---
> v2: Correct MOVSD. Also deal with RCP{P,S}S and RSQRT{P,S}S. Re-work
> <gfni>. Re-base.
These changes are ok for me.
Lili.
next prev parent reply other threads:[~2024-04-25 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:36 [PATCH v2 0/4] x86/APX: respect -msse2avx Jan Beulich
2024-04-19 9:37 ` [PATCH v2 1/4] x86: zap value-less Disp8MemShift from non-EVEX templates Jan Beulich
2024-04-24 6:49 ` Cui, Lili
2024-04-24 7:15 ` Jan Beulich
2024-04-24 13:15 ` Cui, Lili
2024-04-24 13:51 ` Jan Beulich
2024-04-25 5:51 ` Cui, Lili
2024-04-19 9:37 ` [PATCH v2 2/4] x86/APX: extend SSE2AVX coverage Jan Beulich
2024-04-25 6:09 ` Cui, Lili [this message]
2024-04-25 7:22 ` Jan Beulich
2024-04-19 9:38 ` [PATCH v2 3/4] x86/APX: further " Jan Beulich
2024-04-19 9:38 ` [PATCH v2 4/4] x86: tidy <sse*> templates Jan Beulich
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=SJ0PR11MB560046F8FD5CE0817BF848529E172@SJ0PR11MB5600.namprd11.prod.outlook.com \
--to=lili.cui@intel.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).