diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2021-08-14 11:44:46 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2021-08-14 11:44:46 +0200 |
| commit | 240f07805db27cfc746276039c5edccb4c031070 (patch) | |
| tree | db4cfe3e22b014165108e930f6b587a41bba40ef /gcc/tree.h | |
| parent | 261512fa6d56481dc37589e5cb4e288539155d57 (diff) | |
| download | gcc-240f07805db27cfc746276039c5edccb4c031070.zip gcc-240f07805db27cfc746276039c5edccb4c031070.tar.gz gcc-240f07805db27cfc746276039c5edccb4c031070.tar.bz2 | |
i386: Fix ICE with V64QImode broadcast permutation with -mavx512f -mno-avx512bw
The testcase shows another problem, for TARGET_AVX512BW we have a single insn
doing broadcast from the first element, but don't have one for broadcast
of 2nd+ element (so for d->perm[0] we must return false), but for
TARGET_AVX512F && !TARGET_AVX512BW we don't even have support for that other
broadcast. V64QImode case was just added to the AVX2 cases which had
gcc_assert (!TARGET_AVX2 || d->perm[0]);
but for V64QImode we actually need
gcc_assert (!TARGET_AVX512BW || d->perm[0]);
2021-08-14 Jakub Jelinek <jakub@redhat.com>
PR target/101896
* config/i386/i386-expand.c (expand_vec_perm_broadcast_1)
<case E_V64QImode>: For this mode assert
!TARGET_AVX512BW || d->perm[0] rather than !TARGET_AVX2 || d->perm[0].
* gcc.target/i386/avx512f-pr101896.c: New test.
Diffstat (limited to 'gcc/tree.h')
0 files changed, 0 insertions, 0 deletions