public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101896] [12 Regression] ICE in expand_vec_perm_broadcast_1, at config/i386/i386-expand.c:20481 since r12-2837-g50b5877925ef5ae8 Date: Sat, 14 Aug 2021 09:48:15 +0000 [thread overview] Message-ID: <bug-101896-4-JIfevGUWng@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101896-4@http.gcc.gnu.org/bugzilla/> 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 <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:240f07805db27cfc746276039c5edccb4c031070 commit r12-2907-g240f07805db27cfc746276039c5edccb4c031070 Author: Jakub Jelinek <jakub@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 <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.
next prev parent reply other threads:[~2021-08-14 9:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-13 7:26 [Bug target/101896] New: " marxin at gcc dot gnu.org 2021-08-13 7:26 ` [Bug target/101896] " marxin at gcc dot gnu.org 2021-08-13 8:13 ` jakub at gcc dot gnu.org 2021-08-14 9:48 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-14 9:49 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-101896-4-JIfevGUWng@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).