public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
	"Michael Zolotukhin" <michael.v.zolotukhin@gmail.com>
Cc: "Binutils" <binutils@sourceware.org>
Subject: Re: [PATCH] PR gas/16488: Add test for incorrect memory operand for gather/scatter instructions.
Date: Fri, 31 Jan 2014 14:58:00 -0000	[thread overview]
Message-ID: <52EBC83302000078001186A1@nat28.tlf.novell.com> (raw)
In-Reply-To: <CANtU079oJ6oPsQkjn7i4YWuXTcALVYe_WKvDYyMouXePbMOsQw@mail.gmail.com>

>>> On 31.01.14 at 15:38, Michael Zolotukhin <michael.v.zolotukhin@gmail.com> wrote:
>>  You added 2 tests for AT&T syntax, but only 1 for
>> Intel syntax.  Any particular reason for this?
> Yes, the following test doesn't give an error:
>       vgatherqpd zmm6{k1}, ZMMWORD PTR [zmm3]
> I think it's because it is equivalent to something like vgatherqpd
> (,%zmm2,),%zmm6{%k1} (please note commas around zmm2), which also
> doesn't lead to an error.  I assume that in Intel syntax this test is
> regarded as a rich addressing mode, which is acceptable for
> gather/scatters. However, I'm not sure about this - please correct me
> if I'm wrong.

That's correct - the order of registers in a memory address can
get swapped if that results in a valid address.

Jan

  parent reply	other threads:[~2014-01-31 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 10:10 Michael V. Zolotukhin
2014-01-31 14:05 ` H.J. Lu
2014-01-31 14:38   ` Michael Zolotukhin
2014-01-31 14:53     ` H.J. Lu
2014-01-31 14:55       ` Michael Zolotukhin
2014-01-31 14:58     ` Jan Beulich [this message]
2014-01-31 15:35       ` Michael Zolotukhin
2014-01-31 15:41         ` H.J. Lu
2014-01-31 16:06           ` Michael Zolotukhin
2014-01-31 16:26             ` H.J. Lu
2014-01-31 16:31               ` Michael Zolotukhin

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=52EBC83302000078001186A1@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=michael.v.zolotukhin@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).