From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH v3 09/10] x86-64: honor vendor specifics for near RET
Date: Mon, 13 Jan 2020 17:40:00 -0000 [thread overview]
Message-ID: <CAMe9rOp3k3QJitTM6+U=UAtkq6optJS=C3UfJB7EHG_zz-X1Mg@mail.gmail.com> (raw)
In-Reply-To: <17e6bb1e-8a68-947e-957d-f469fa894e76@suse.com>
On Fri, Dec 27, 2019 at 1:21 AM Jan Beulich <JBeulich@suse.com> wrote:
>
> While vendors agree about default operand size (64 bits) and hence
> unavilability of a 32-bit form, AMD honors a 16-bit operand size
> override (0x66) while Intel doesn't.
>
OK.
Thanks.
--
H.J.
next prev parent reply other threads:[~2020-01-13 17:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 9:13 [PATCH v3 00/10] x86: operand size handling improvements Jan Beulich
2019-12-27 9:18 ` [PATCH v3 05/10] x86-64: also support MOVSXD with 16-bit destination Jan Beulich
2019-12-27 9:18 ` [PATCH v3 04/10] x86: replace adhoc ambiguous operand checking for MOVSX/MOVZX Jan Beulich
2019-12-27 9:19 ` [PATCH v3 02/10] x86: replace adhoc ambiguous operand checking for CRC32 Jan Beulich
2020-01-13 17:27 ` H.J. Lu
2019-12-27 9:20 ` [PATCH v3 06/10] x86: correct VFPCLASSP{S,D} operand size handling Jan Beulich
2020-01-13 17:36 ` H.J. Lu
2019-12-27 9:20 ` [PATCH v3 07/10] x86: drop further pointless/bogus DefaultSize Jan Beulich
2020-01-13 17:37 ` H.J. Lu
2019-12-27 9:20 ` [PATCH v3 08/10] x86-64: also diagnose far returns / IRET with ambiguous operand size Jan Beulich
2020-01-13 17:38 ` H.J. Lu
2019-12-27 9:21 ` [PATCH v3 09/10] x86-64: honor vendor specifics for near RET Jan Beulich
2020-01-13 17:40 ` H.J. Lu [this message]
2019-12-27 9:22 ` [PATCH v3 01/10] x86: improve handling of insns with ambiguous operand sizes Jan Beulich
2020-01-03 8:32 ` Jan Beulich
2020-01-09 22:36 ` H.J. Lu
2020-01-10 8:54 ` Jan Beulich
2020-01-10 20:46 ` H.J. Lu
2020-01-13 12:57 ` Jan Beulich
2020-01-13 14:45 ` H.J. Lu
2019-12-27 9:24 ` [PATCH v3 03/10] x86: move certain MOVSX/MOVZX tests Jan Beulich
2020-01-13 17:33 ` H.J. Lu
2020-01-20 15:31 ` Jan Beulich
2020-01-20 15:34 ` H.J. Lu
2020-01-22 11:03 ` Jan Beulich
2020-01-22 12:20 ` H.J. Lu
2020-01-22 16:04 ` Jan Beulich
2020-01-22 16:09 ` H.J. Lu
2020-01-22 16:28 ` Jan Beulich
2020-01-22 17:32 ` H.J. Lu
2020-01-23 10:38 ` Jan Beulich
2020-01-23 12:53 ` H.J. Lu
2020-01-23 13:13 ` Jan Beulich
2020-01-23 13:43 ` H.J. Lu
2019-12-27 9:27 ` [PATCH v3 10/10] x86-64: Intel64 adjustments for insns dealing with far pointers Jan Beulich
2020-01-13 17:43 ` H.J. Lu
2020-01-14 15:01 ` Jan Beulich
2020-01-14 17:06 ` H.J. Lu
2020-01-15 7:49 ` Jan Beulich
2020-01-15 13:29 ` H.J. Lu
2020-01-15 17:03 ` Jan Beulich
2020-01-15 21:59 ` H.J. Lu
2020-01-16 9:16 ` Jan Beulich
2020-01-16 14:58 ` H.J. Lu
2020-01-16 15:14 ` Jan Beulich
2020-01-16 20:25 ` H.J. Lu
2020-01-17 11:48 ` Jan Beulich
2020-01-17 18:06 ` H.J. Lu
2020-01-20 10:12 ` Jan Beulich
2020-01-20 13:43 ` H.J. Lu
2020-01-20 14:34 ` Jan Beulich
2020-01-22 13:22 ` H.J. Lu
2020-01-22 14:24 ` Jan Beulich
2020-01-22 14:34 ` 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='CAMe9rOp3k3QJitTM6+U=UAtkq6optJS=C3UfJB7EHG_zz-X1Mg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
/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).