This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH v3 06/10] x86: correct VFPCLASSP{S,D} operand size handling
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Jan Beulich <JBeulich at suse dot com>
- Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
- Date: Mon, 13 Jan 2020 09:36:07 -0800
- Subject: Re: [PATCH v3 06/10] x86: correct VFPCLASSP{S,D} operand size handling
- References: <a79874b2-6fcd-d65f-1163-2c9d1d8f4826@suse.com> <e9b66b9a-35ac-7eba-ccff-df678ea318c7@suse.com>
On Fri, Dec 27, 2019 at 1:20 AM Jan Beulich <JBeulich@suse.com> wrote:
>
> With AVX512VL disabled (e.g. when writing code for the Knights family
> of processors) these insns aren't ambiguous when used with a memory
> source, and hence should be accepted without suffix or operand size
> specifier. When AVX512VL is enabled, to be consistent with this as
> well as other ambiguous operand size handling it seems better to just
> warn about the ambiguity in AT&T mode, and still default to 512-bit
> operands (on the assumption that the code may have been written without
> AVX512VL in mind yet).
>
>
For AT&T syntax, I don't want special treatment for AVX512VL. They
should require suffix even if AVX512VL is disabled.
--
H.J.