From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH 2/3] Add check for 8-bit old registers in EVEX format
Date: Wed, 22 May 2024 02:20:31 +0000 [thread overview]
Message-ID: <SJ0PR11MB56003FAAB6AD8336AFDCEAE19EEB2@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <d11158f8-3dce-45c0-9de3-b03f15c9097f@suse.com>
> To avoid these diagnostics getting yet more diffuse, can you please switch to
>
> as_bad (_("can't encode register '%s%s' in an "
> "instruction requiring %s prefix"),
> register_prefix, i.op[x].regs->reg_name,
> i.tm.opcode_modifier.evex ? "EVEX" : "REX/REX2");
>
> Okay with that (or a substantially similar; I didn't test the above, after
> all) adjustment.
>
It's correct, thanks for the suggestions, submitted both patches.
Lili.
next prev parent reply other threads:[~2024-05-22 2:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 6:21 [PATCH 0/3] Support APX zero-upper Cui, Lili
2024-05-20 6:22 ` [PATCH 1/3] x86: Split REX/REX2 old registers judgment Cui, Lili
2024-05-21 12:18 ` Jan Beulich
2024-05-22 1:33 ` Cui, Lili
2024-05-22 5:49 ` Jan Beulich
2024-05-22 6:11 ` Cui, Lili
2024-05-22 6:22 ` Jan Beulich
2024-05-20 6:22 ` [PATCH 2/3] Add check for 8-bit old registers in EVEX format Cui, Lili
2024-05-21 12:24 ` Jan Beulich
2024-05-22 2:20 ` Cui, Lili [this message]
2024-05-20 6:22 ` [PATCH 3/3] Support APX zero-upper Cui, Lili
2024-05-22 6:21 ` Jan Beulich
2024-05-22 8:05 ` 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=SJ0PR11MB56003FAAB6AD8336AFDCEAE19EEB2@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).