From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Subject: [PATCH 0/6] x86: further opcode table compaction plus fallout
Date: Fri, 26 Mar 2021 11:48:41 +0100 [thread overview]
Message-ID: <287ad145-1fe3-2477-327a-30e8d45a4be7@suse.com> (raw)
This continues from "[PATCH 0/8] x86: work towards further opcode table
compaction", but there will remain significant gains to be had. It also
remains open whether to also convert VEX/EVEX Space_0F* use into
opcode representation, just like patch 4 does as a side effect of
templating SSE2AVX and their "original" templates.
1: derive opcode encoding space attribute from base opcode
2: shrink some struct insn_template fields
3: undo Prefix_0X<nn> use in opcode table
4: fold SSE2AVX and their base MMX/SSE templates
5: VPSADBW's source operands are also commutative
6: move some opcode table entries
Jan
next reply other threads:[~2021-03-26 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 10:48 Jan Beulich [this message]
2021-03-26 10:50 ` [PATCH 1/6] x86: derive opcode encoding space attribute from base opcode Jan Beulich
2021-03-26 10:50 ` [PATCH 2/6] x86: shrink some struct insn_template fields Jan Beulich
2021-03-29 13:00 ` H.J. Lu
2021-03-29 14:03 ` Jan Beulich
2021-03-29 14:41 ` H.J. Lu
2021-03-29 14:49 ` Jan Beulich
2021-03-29 14:51 ` H.J. Lu
2021-03-26 10:51 ` [PATCH 3/6] x86: undo Prefix_0X<nn> use in opcode table Jan Beulich
2021-03-26 10:51 ` [PATCH 4/6] x86: fold SSE2AVX and their base MMX/SSE templates Jan Beulich
2021-03-29 13:31 ` H.J. Lu
2021-03-26 10:52 ` [PATCH 5/6] x86: VPSADBW's source operands are also commutative Jan Beulich
2021-03-26 10:53 ` [PATCH 6/6] x86: move some opcode table entries Jan Beulich
2021-03-26 21:16 ` [PATCH 0/6] x86: further opcode table compaction plus fallout H.J. Lu
2021-03-29 10:08 ` 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=287ad145-1fe3-2477-327a-30e8d45a4be7@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@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).