From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/9] x86: disassembler fixes and table shrinking
Date: Tue, 9 Mar 2021 06:27:12 -0800 [thread overview]
Message-ID: <CAMe9rOo81tWfbx4PL8VQOLWHzgr6+8zppyT2jNUya+cwFqe=qw@mail.gmail.com> (raw)
In-Reply-To: <59d65321-4135-a723-be53-2450c3759c35@suse.com>
On Tue, Mar 9, 2021 at 5:05 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> The first and last patches are bug fixes. Most of the others
> rearrange the order of decoding of relevant parts of the insn,
> with the goal of shrinking overall table sizes. This goes
> along the lines of earlier changes towards the same goal.
>
> If I had recognized earlier the issue the last patch fixes, I
> would have put it near the beginning of this series. Re-
> basing ahead, however, turned out rather undesirable.
>
> 1: correct decoding of nop/reserved space (0f18 ... 0x1f)
> 2: re-arrange order of decode for various legacy opcodes
> 3: re-arrange order of decode for various VEX opcodes
> 4: re-arrange order of decode for various mask reg opcodes
> 5: re-arrange order of decode for various EVEX opcodes
> 6: reuse VEX entries for EVEX vperm{q,pd}
> 7: reuse further VEX entries for EVEX
> 8: rearrange enumerator and table entry order
> 9: Intel: correct AVX512 S/G disassembly
>
OK for all.
Thanks.
--
H.J.
prev parent reply other threads:[~2021-03-09 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 13:05 Jan Beulich
2021-03-09 13:06 ` [PATCH 1/9] x86: correct decoding of nop/reserved space (0f18 ... 0x1f) Jan Beulich
2021-03-09 13:06 ` [PATCH 2/9] x86: re-arrange order of decode for various legacy opcodes Jan Beulich
2021-03-09 13:07 ` [PATCH 3/9] x86: re-arrange order of decode for various VEX opcodes Jan Beulich
2021-03-09 13:07 ` [PATCH 4/9] x86: re-arrange order of decode for various mask reg opcodes Jan Beulich
2021-03-09 13:10 ` [PATCH 5/9] x86: re-arrange order of decode for various EVEX opcodes Jan Beulich
2021-03-09 13:10 ` [PATCH 6/9] x86: reuse VEX entries for EVEX vperm{q,pd} Jan Beulich
2021-03-09 13:11 ` [PATCH 7/9] x86: reuse further VEX entries for EVEX Jan Beulich
2021-03-09 13:12 ` [PATCH 8/9] x86: rearrange enumerator and table entry order Jan Beulich
2021-03-09 13:12 ` [PATCH 9/9] x86/Intel: correct AVX512 S/G disassembly Jan Beulich
2021-03-09 14:27 ` H.J. Lu [this message]
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='CAMe9rOo81tWfbx4PL8VQOLWHzgr6+8zppyT2jNUya+cwFqe=qw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--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).