From: "Cui, Lili" <lili.cui@intel.com>
To: binutils@sourceware.org
Cc: hjl.tools@gmail.com, jbeulich@suse.com
Subject: [PATCH V2 0/3] x86: Optimize the encoder of the vvvv register
Date: Tue, 30 Apr 2024 18:40:01 +0800 [thread overview]
Message-ID: <20240430104004.3048944-1-lili.cui@intel.com> (raw)
These patches want to optimize the encoder of the vvvv register.
Previously we used Vexvvvv, SWAP_SOURCES and extension_opcode to help encode the vvvv register, these patches simplified the logic to only use vexvvvv and added appropriate Vexvvvv values for the related instructions.
V2: Added more comments in the code and removed changes to the SwapSources template and push2/POP2 to avoid modifying some places twice.
Cui, Lili (3):
x86: Use vexvvvv as the switch state to encode the vvvv register
x86: Drop SwapSources
x86: Drop using extension_opcode to encode vvvv register
gas/config/tc-i386.c | 58 +-
gas/testsuite/gas/i386/x86-64-sse2avx.d | 7 +
gas/testsuite/gas/i386/x86-64-sse2avx.s | 7 +
opcodes/i386-opc.h | 21 +-
opcodes/i386-opc.tbl | 1156 ++++++++++++-----------
5 files changed, 635 insertions(+), 614 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-30 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 10:40 Cui, Lili [this message]
2024-04-30 10:40 ` [PATCH v2 1/3] x86: Use vexvvvv as the switch state to encode " Cui, Lili
2024-04-30 15:27 ` Jan Beulich
2024-04-30 10:40 ` [PATCH V2 2/3] x86: Drop SwapSources Cui, Lili
2024-04-30 15:28 ` Jan Beulich
2024-04-30 10:40 ` [PATCH V2 3/3] x86: Drop using extension_opcode to encode vvvv register Cui, Lili
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=20240430104004.3048944-1-lili.cui@intel.com \
--to=lili.cui@intel.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jbeulich@suse.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).