From: "Hu, Lin1" <lin1.hu@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>, "Cui, Lili" <lili.cui@intel.com>
Cc: "Lu, Hongjiu" <hongjiu.lu@intel.com>,
"ccoutant@gmail.com" <ccoutant@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH 1/6] Support {evex} pseudo prefix for decode evex promoted insns without egpr32.
Date: Mon, 25 Sep 2023 01:35:59 +0000 [thread overview]
Message-ID: <SJ0PR11MB5940C9767F9EC1F5665F5ADAA6FCA@SJ0PR11MB5940.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4cbdb126-6995-ead9-0318-f41674ef5527@suse.com>
Indeed, it belong to the previous apx patch. But this commit just got done, so followed this patch out.
BRs,
Lin
-----Original Message-----
From: Jan Beulich <jbeulich@suse.com>
Sent: Friday, September 22, 2023 5:13 PM
To: Cui, Lili <lili.cui@intel.com>
Cc: Lu, Hongjiu <hongjiu.lu@intel.com>; ccoutant@gmail.com; Hu, Lin1 <lin1.hu@intel.com>; binutils@sourceware.org
Subject: Re: [PATCH 1/6] Support {evex} pseudo prefix for decode evex promoted insns without egpr32.
On 21.09.2023 12:11, Cui, Lili wrote:
> From: "Hu, Lin1" <lin1.hu@intel.com>
>
> gas/ChangeLog:
>
> * config/tc-i386.c (match_template): Support D for APX_F insns
> with 2 operands.
Without having looked at the full patch yet - this change hardly belongs here.
Jan
next prev parent reply other threads:[~2023-09-25 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 10:11 [PATCH 0/6] [RFC] Support Intel APX EGPR (part II) Cui, Lili
2023-09-21 10:11 ` [PATCH 1/6] Support {evex} pseudo prefix for decode evex promoted insns without egpr32 Cui, Lili
2023-09-22 9:13 ` Jan Beulich
2023-09-25 1:35 ` Hu, Lin1 [this message]
2023-09-28 14:36 ` Jan Beulich
2023-09-21 10:11 ` [PATCH 2/6] Disable pseudo prefix {rex2} for illegal instructions Cui, Lili
2023-09-28 14:53 ` Jan Beulich
2023-09-21 10:11 ` [PATCH 3/6] x86-64: Add R_X86_64_CODE_4_GOTPCRELX Cui, Lili
2023-09-21 10:11 ` [PATCH 4/6] gold: Handle R_X86_64_CODE_4_GOTPCRELX Cui, Lili
2023-09-21 10:11 ` [PATCH 5/6] For Cui, Lili
2023-09-21 10:11 ` [PATCH 6/6] Gold: Handle R_X86_64_CODE_4_GOTPC32_TLSDESC/R_X86_64_CODE_4_GOTTPOFF 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=SJ0PR11MB5940C9767F9EC1F5665F5ADAA6FCA@SJ0PR11MB5940.namprd11.prod.outlook.com \
--to=lin1.hu@intel.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=hongjiu.lu@intel.com \
--cc=lili.cui@intel.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).