From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86/Intel: accept mandated operand order for vcvt{,u}si2s{d,s}
Date: Thu, 23 Apr 2015 12:39:00 -0000 [thread overview]
Message-ID: <CAMe9rOomWLMwQT6R2qLr1p7_dzmwuNLsz2PEk-6tV3NTt_=24Q@mail.gmail.com> (raw)
In-Reply-To: <552FE0630200007800072CD0@mail.emea.novell.com>
On Thu, Apr 16, 2015 at 7:16 AM, Jan Beulich <JBeulich@suse.com> wrote:
> As pointed out before, the documentation mandates the rounding mode to
> follow the GPR, so gas should accept such input. As the brojen code got
> released already we sadly will need to continue to also accept the
> badly ordered operands.
>
> gas/testsuite/
> 2015-04-16 Jan Beulich <jbeulich@suse.com>
>
> * gas/i386/avx512f-intel.d: Adjust expectations on operand order.
> * gas/i386/evex-lig256-intel.d: Likewise.
> * gas/i386/evex-lig512-intel.d: Likewise.
> * gas/i386/x86-64-avx512f-intel.d: Likewise.
> * gas/i386/x86-64-evex-lig256-intel.d: Likewise.
> * gas/i386/x86-64-evex-lig512-intel.d: Likewise.
>
> opcodes/
> 2015-04-16 Jan Beulich <jbeulich@suse.com>
>
> * i386-opc.tbl: New IntelSyntax entries for vcvt{,u}si2s{d,s}.
> * i386-tbl.h: Regenerate.
>
I checked with our people. Intel Software Developer Manual only governs
the output side of the binary form of instruction byte stream matches what
HW expect. Each assembly tool product has its own implementation of
transforming the input language/dialect into the output stream. In case of
GNU assembler, operand order for AT&T and Intel syntax for AVX512 is
the one used in AVX512 testcases.
It is not OK.
--
H.J.
next prev parent reply other threads:[~2015-04-23 12:39 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 [this message]
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
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='CAMe9rOomWLMwQT6R2qLr1p7_dzmwuNLsz2PEk-6tV3NTt_=24Q@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).