[PATCH v3 06/10] x86: correct VFPCLASSP{S,D} operand size handling

[H.J. Lu]

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.