[Bug target/89229] Incorrect xmm16-xmm31/ymm16-ymm31 in vector move

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229

--- Comment #33 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <h...@gcc.gnu.org>:

https://gcc.gnu.org/g:9d74caf21be7025db8fef997e87ebf3b85acaf4a

commit r10-7182-g9d74caf21be7025db8fef997e87ebf3b85acaf4a
Author: H.J. Lu <hjl.to...@gmail.com>
Date:   Sun Mar 15 10:21:08 2020 -0700

    i386: Use ix86_output_ssemov for SFmode TYPE_SSEMOV

    There is no need to set mode attribute to V16SFmode since
ix86_output_ssemov
    can properly encode xmm16-xmm31 registers with and without AVX512VL.

    gcc/

            PR target/89229
            * config/i386/i386.c (ix86_output_ssemov): Handle MODE_SI and
            MODE_SF.
            * config/i386/i386.md (*movsf_internal): Call ix86_output_ssemov
            for TYPE_SSEMOV.  Remove TARGET_PREFER_AVX256, TARGET_AVX512VL
            and ext_sse_reg_operand check.

    gcc/testsuite/

            PR target/89229
            * gcc.target/i386/pr89229-6a.c: New test.
            * gcc.target/i386/pr89229-6b.c: Likewise.
            * gcc.target/i386/pr89229-6c.c: Likewise.