[Bug target/94942] [10/11 Regression] ICE: in extract_constrain_insn, at recog.c:2195 (insn does not satisfy its constraints) with -O -flive-range-shrinkage -ftree-vrp -mavx512vl

[cvs-commit at gcc dot gnu.org]

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <ja...@gcc.gnu.org>:

https://gcc.gnu.org/g:7f916201ac390a5e1c88562bb91b1b4ab2852f22

commit r11-64-g7f916201ac390a5e1c88562bb91b1b4ab2852f22
Author: Jakub Jelinek <ja...@redhat.com>
Date:   Tue May 5 11:33:47 2020 +0200

    x86: Fix *vec_dupv4hi constraints [PR94942]

    This insn and split splits into HI->V?HImode broadcast for avx2 and later,
    but either the operands need to be %xmm0-%xmm15 (i.e. VEX encoded insn), or
    the insn needs both AVX512BW and AVX512VL.
    Now, Yv constraint is v for AVX512VL and x otherwise, so for -mavx512vl
-mno-avx512bw
    we ICE if we end up with a %xmm16+ register from RA.
    Yw constraint is v for AVX512VL and AVX512BW and nothing otherwise, so
    in this pattern we actually need xYw.

    2020-05-05  Jakub Jelinek  <ja...@redhat.com>

            PR target/94942
            * config/i386/mmx.md (*vec_dupv4hi): Use xYw constraints instead of
Yv.

            * gcc.target/i386/pr94942.c: New test.