From: Hongtao Liu <crazylht@gmail.com>
To: "Cui, Lili" <lili.cui@intel.com>
Cc: "Beulich, Jan" <JBeulich@suse.com>,
Binutils <binutils@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] x86/Intel: SHLD/SHRD have dual meaning
Date: Mon, 22 Apr 2024 15:47:44 +0800 [thread overview]
Message-ID: <CAMZc-bzv4G0sg7PgP4oLMXyGhrYsp28dQkniyf8d85+-80F7OA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR11MB560099E06545D2591C9B56CE9E122@SJ0PR11MB5600.namprd11.prod.outlook.com>
On Mon, Apr 22, 2024 at 3:44 PM Cui, Lili <lili.cui@intel.com> wrote:
>
> > On 22.04.2024 06:09, Hongtao Liu wrote:
> > > On Fri, Apr 19, 2024 at 5:29 PM Jan Beulich <jbeulich@suse.com> wrote:
> > >>
> > >> Since we uniformly permit D suffixes in Intel mode whenever in AT&T
> > >> mode an L suffix may be used, we need to be consistent with this.
> > > I think we need to forbid the D suffix for APX NDD SHL/SHR under Intel
> > > mode to avoid ambiguity.
> >
> > Hmm. Special casing just two insns is out of question imo (in fact that's what
> > is - unintentionally - partly happening prior to the change here).
> >
I know the suffix L is needed in AT&T mode to specify the operand
size to avoid ambiguity.
But why do we need the suffix D for Intel mode?
--
BR,
Hongtao
next prev parent reply other threads:[~2024-04-22 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:28 Jan Beulich
2024-04-22 4:09 ` Hongtao Liu
2024-04-22 6:51 ` Jan Beulich
2024-04-22 7:43 ` Cui, Lili
2024-04-22 7:47 ` Hongtao Liu [this message]
2024-04-22 8:42 ` Jan Beulich
2024-04-22 11:36 ` Hongtao Liu
2024-04-22 8:45 ` 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=CAMZc-bzv4G0sg7PgP4oLMXyGhrYsp28dQkniyf8d85+-80F7OA@mail.gmail.com \
--to=crazylht@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).