From: "Jan Beulich" <JBeulich@suse.com>
To: "Kirill Yukhin" <kirill.yukhin@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"Binutils" <binutils@sourceware.org>,"H. Peter Anvin"
<hpa@zytor.com>
Subject: Re: [PATCH] x86/Intel: accept mandated operand order for vcvt{,u}si2s{d,s}
Date: Tue, 26 May 2015 12:18:00 -0000 [thread overview]
Message-ID: <5564807F020000780007DE21@mail.emea.novell.com> (raw)
In-Reply-To: <20150526112416.GC9967@msticlxl57.ims.intel.com>
>>> On 26.05.15 at 13:24, <kirill.yukhin@gmail.com> wrote:
> Finally, (I promise, I repeat it last time) as far as SDM is not a source of
> Intel syntax,
Which btw is something I don't really buy, for three reasons:
1) Why would it specify mnemonics (including operands) then in the
first place?
2) Other architectures explicitly use the instruction specifications as
guideline for what assemblers should accept, or even require
assemblers to behave in a certain way (see e.g. ARM ARM).
3) In the absence of any other formal definition, one ought to use
what is there instead of inventing something new.
> I see no reason to allow another order. IMO, such addition might
> even increase confusion about this non-trivial stuff.
Quite the opposite - it eliminates some confusion: Just compare
vcvtsd2ss xmm6\{k7\},xmm5,xmm4,\{rn-sae\}
and
vcvtsi2ss xmm6,xmm5,\{rn-sae\},eax
(found in the unpatched testsuite). In the former and all other
instructions (excepting the questionable ones) the rounding
specifier goes after all source operands.
Jan
next prev parent reply other threads:[~2015-05-26 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:16 Jan Beulich
2015-04-23 12:39 ` H.J. Lu
2015-04-23 13:06 ` Jan Beulich
2015-04-23 13:17 ` H.J. Lu
2015-04-23 13:48 ` Jan Beulich
2015-04-23 13:53 ` H.J. Lu
2015-05-05 16:07 ` Jan Beulich
2015-05-05 16:10 ` H.J. Lu
2015-05-06 7:44 ` Jan Beulich
2015-05-21 6:30 ` Jan Beulich
2015-05-21 10:42 ` H.J. Lu
2015-05-21 11:37 ` Jan Beulich
2015-05-21 12:07 ` H.J. Lu
2015-05-21 15:03 ` Jan Beulich
2015-05-21 15:12 ` H.J. Lu
2015-05-21 16:05 ` Jan Beulich
2015-05-25 14:56 ` Kirill Yukhin
2015-05-26 8:04 ` Jan Beulich
2015-05-26 11:25 ` Kirill Yukhin
2015-05-26 12:18 ` Jan Beulich [this message]
2015-06-01 9:17 ` Mark Wielaard
2015-06-01 9:23 ` Jan Beulich
2015-06-01 9:41 ` 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=5564807F020000780007DE21@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=kirill.yukhin@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).