From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kirill.yukhin@intel.com, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 5/6] x86/MPX: fix operand size handling
Date: Thu, 10 Oct 2013 15:14:00 -0000 [thread overview]
Message-ID: <CAMe9rOpZzcN3DcFUTw1A7Q1n5aGxD8MeCejvnrDwjD48Mr96-g@mail.gmail.com> (raw)
In-Reply-To: <5256C43B02000078000FA37F@nat28.tlf.novell.com>
On Thu, Oct 10, 2013 at 6:14 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 09.10.13 at 17:51, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>> On Wed, Oct 9, 2013 at 12:36 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>>> On 08.10.13 at 17:45, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>>>> On Tue, Oct 8, 2013 at 7:43 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> All MPX instructions in 64-bit mode ignore REX.W, which means we neither
>>>>> need to encode this bit nor should disassemble with 32-bit register
>>>>> operands.
>>>>>
>>>>> No MPX instructions would ever take a 16-bit register operand.
>>>>>
>>>>> gas/
>>>>> 2013-10-08 Jan Beulich <jbeulich@suse.com>
>>>>>
>>>>> * tc-i386.c (process_suffix): Warn about 32-bit register operands
>>>>> to MPX instructions in 64-bit mode.
>>>>
>>>> I think it should be an error.
>>>
>>> I can certainly change that - a warning just seemed a better match
>>> to hardware ignoring operand size here.
>>
>> We can use separate entries with Reg32 for CpuNo64 and Reg64 for Cpu64,
>> similar to mov with debug registers. Let's do that instead.
>
> Here's the updated patch.
>
> Jan
>
> General purpose register operands of MPX instructions can only ever be
> native size ones.
>
> opcodes/
> 2013-10-08 Jan Beulich <jbeulich@suse.com>
>
> * i386-dis.c (intel_operand_size): Move v_bnd_mode alongside the
> default case.
> (OP_E_register): Move v_bnd_mode alongside m_mode.
> * i386-opc.tbl (bndcl, bndcu, bndcn): Split 32- and 64-bit variants.
> Drop Reg16 and Disp16. Add NoRex64.
> (bndmk, bndmov, bndldx, bndstx): Drop Disp16.
> * i386-tbl.h: Re-generate.
>
It is OK.
Thanks.
H.J.
next prev parent reply other threads:[~2013-10-10 15:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 14:36 [PATCH 0/6] x86: various MPX fixes Jan Beulich
2013-10-08 14:41 ` [PATCH 1/6] x86/MPX: testsuite adjustments Jan Beulich
2013-10-08 14:41 ` [PATCH 2/6] x86/MPX: fix address size handling Jan Beulich
2013-10-08 15:15 ` H.J. Lu
2013-10-08 15:20 ` Jan Beulich
2013-10-08 15:32 ` H.J. Lu
2013-10-09 7:30 ` Jan Beulich
2013-10-09 15:45 ` H.J. Lu
2013-10-10 12:27 ` Jan Beulich
2013-10-10 15:18 ` H.J. Lu
2013-10-08 14:42 ` [PATCH 3/6] x86/MPX: suppress base/index swapping in Intel mode for bndmk, bndldx, and bndstx Jan Beulich
2013-10-08 15:16 ` H.J. Lu
2013-10-08 15:23 ` Jan Beulich
2013-10-08 15:34 ` H.J. Lu
2013-10-08 16:00 ` Jan Beulich
2013-10-08 16:19 ` H.J. Lu
2013-10-09 7:15 ` acceptance rules (was: Re: [PATCH 3/6] x86/MPX: suppress base/index swapping ...) Jan Beulich
2013-10-09 16:45 ` H.J. Lu
2013-10-08 14:43 ` [PATCH 4/6] x86/MPX: bndmk, bndldx, and bndstx only allow a memory operand Jan Beulich
2013-10-08 15:28 ` H.J. Lu
2013-10-09 7:24 ` Jan Beulich
2013-10-09 15:17 ` H.J. Lu
2013-10-08 14:43 ` [PATCH 5/6] x86/MPX: fix operand size handling Jan Beulich
2013-10-08 15:45 ` H.J. Lu
2013-10-09 7:36 ` Jan Beulich
2013-10-09 15:51 ` H.J. Lu
2013-10-10 13:14 ` Jan Beulich
2013-10-10 15:14 ` H.J. Lu [this message]
2013-10-12 15:58 ` H.J. Lu
2013-10-12 17:12 ` H.J. Lu
2013-10-08 14:44 ` [PATCH 6/6] x86/MPX: bndmk, bndldx, and bndstx don't allow RIP-relative addressing Jan Beulich
2013-10-08 16:13 ` H.J. Lu
2013-10-09 7:40 ` 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=CAMe9rOpZzcN3DcFUTw1A7Q1n5aGxD8MeCejvnrDwjD48Mr96-g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=kirill.yukhin@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).