This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] x86: don't require operand size specification for AVX512 broadcasts
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Jan Beulich <JBeulich at suse dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Thu, 23 Apr 2015 05:48:50 -0700
- Subject: Re: [PATCH] x86: don't require operand size specification for AVX512 broadcasts
- Authentication-results: sourceware.org; auth=none
- References: <552FEA900200007800072D49 at mail dot emea dot novell dot com>
On Thu, Apr 16, 2015 at 8:00 AM, Jan Beulich <JBeulich@suse.com> wrote:
> Certain conversion operations as well as vfpclassp{d,s} are ambiguous
> when the input operand is in memory. That ambiguity, however, doesn't
> apply when using broadcasts (the destination operand size can be
> induced from the broadcast specifier).
>
> gas/
> 2015-04-16 Jan Beulich <jbeulich@suse.com>
>
> * config/tc-i386.c (match_mem_size): Also allow no size
> specification when broadcasting.
>
> gas/testsuite/
> 2015-04-16 Jan Beulich <jbeulich@suse.com>
>
> * gas/i386/avx512dq.s: Drop 'z' suffix from vfpclassp{d,s} in
> some AT&T and all Intel cases.
> * gas/i386/x86-64-avx512dq.s: Likewise.
> * gas/i386/avx512dq_vl.s: Drop 'x' and 'y' suffixes from
> vcvt{,u}qq2ps and vfpclassp{d,s} in some AT&T and all Intel
> cases.
> * gas/i386/x86-64-avx512dq_vl.s: Likewise.
> * gas/i386/avx512f_vl.s: Drop 'x' and 'y' suffixes from
> vcvt{,t}pd2{,u}dq and vcvtpd2ps in some AT&T and all Intel
> cases.
> * gas/i386/x86-64-avx512f_vl.s: Likewise.
>
It is OK. Thanks.
--
H.J.