From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH 6/8] x86: re-number PREFIX_0X<nn>
Date: Mon, 22 Mar 2021 11:03:29 -0700 [thread overview]
Message-ID: <YFjb8QmbOtMmwTAr@gmail.com> (raw)
In-Reply-To: <67c381fe-2030-7750-d258-6257174100c3@suse.com>
On Mon, Mar 22, 2021 at 05:45:30PM +0100, Jan Beulich wrote:
> In preparation to use PREFIX_0X<nn> attributes also in VEX/XOP/EVEX
> encoding templates, renumber the pseudo-enumerators such that their
> values can then also be used directly in the respective prefix bit
> fields.
>
> gas/
> 2021-03-XX Jan Beulich <jbeulich@suse.com>
>
> * config/tc-i386.c (pte): Re-order opc_pfx[] entries.
>
> opcodes/
> 2021-03-XX Jan Beulich <jbeulich@suse.com>
>
> * i386-opc.h (PREFIX_0XF2, PREFIX_0XF3): Excahnge values. Extend
> comment.
> * i386-tbl.h: Re-generate.
>
OK. Thanks.
H.J.
next prev parent reply other threads:[~2021-03-22 18:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 16:40 [PATCH 0/8] x86: work towards further opcode table compaction Jan Beulich
2021-03-22 16:42 ` [PATCH 1/8] x86: unbreak certain MPX insn operand forms Jan Beulich
2021-03-22 17:58 ` H.J. Lu
2021-03-22 16:42 ` [PATCH 2/8] x86: don't open-code PREFIX_NONE Jan Beulich
2021-03-22 17:58 ` H.J. Lu
2021-03-22 16:43 ` [PATCH 3/8] x86: don't use opcode_length to identify pseudo prefixes Jan Beulich
2021-03-22 17:55 ` H.J. Lu
2021-03-23 7:36 ` Jan Beulich
2021-03-23 12:05 ` H.J. Lu
2021-03-23 16:42 ` [PATCH v2] " Jan Beulich
2021-03-23 18:32 ` H.J. Lu
2021-03-22 16:44 ` [PATCH 5/8] x86: re-order two fields of struct insn_template Jan Beulich
2021-03-22 18:03 ` H.J. Lu
2021-03-22 16:45 ` [PATCH 6/8] x86: re-number PREFIX_0X<nn> Jan Beulich
2021-03-22 18:03 ` H.J. Lu [this message]
2021-03-22 16:46 ` [PATCH 7/8] x86: derive mandatory prefix attribute from base opcode Jan Beulich
2021-03-22 18:03 ` H.J. Lu
2021-03-23 16:36 ` Jan Beulich
2021-03-23 18:34 ` H.J. Lu
2021-03-24 7:27 ` Jan Beulich
2021-03-24 13:43 ` H.J. Lu
[not found] ` <65b17a6a-cc6a-a706-5e95-a7284c45beb1@suse.com>
2021-03-22 18:02 ` [PATCH 8/8] x86: derive opcode length from opcode value H.J. Lu
[not found] ` <f116024a-077d-c64e-f37c-1da8299272f0@suse.com>
2021-03-22 18:04 ` [PATCH 4/8] x86: split opcode prefix and opcode space representation 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=YFjb8QmbOtMmwTAr@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).