https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101896
--- Comment #2 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:240f07805db27cfc746276039c5edccb4c031070 commit r12-2907-g240f07805db27cfc746276039c5edccb4c031070 Author: Jakub Jelinek <ja...@redhat.com> Date: Sat Aug 14 11:44:46 2021 +0200 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 <ja...@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.
