From: Hongtao Liu <crazylht@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] i386: Fix up V32HImode permutations with -mno-avx512bw [PR101860]
Date: Thu, 12 Aug 2021 16:52:12 +0800 [thread overview]
Message-ID: <CAMZc-by00qZO=YsiOgj5w4ZOffdcHd2sS7dcK9LnKcbW3TG9Fw@mail.gmail.com> (raw)
In-Reply-To: <20210812074927.GW2380545@tucnak>
On Thu, Aug 12, 2021 at 3:49 PM Jakub Jelinek <jakub@redhat.com> wrote:
>
> Hi!
>
> My patch from yesterday apparently broke some V32HImode permutations
> as the testcase shows.
> The first function assumed it would never be called in d->testing_p mode
> and so went right away into emitting the code.
> And the second one assumed V32HImode would never reach it, which now
> can for the !TARGET_AVX512BW case. We don't have a instruction
> in that case though.
>
> Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for
> trunk?
LGTM.
>
> 2021-08-12 Jakub Jelinek <jakub@redhat.com>
>
> PR target/101860
> * config/i386/i386-expand.c (ix86_expand_vec_one_operand_perm_avx512):
> If d->testing_p, return true after performing checks instead of
> actually expanding the insn.
> (expand_vec_perm_broadcast_1): Handle V32HImode - assert
> !TARGET_AVX512BW and return false.
>
> * gcc.target/i386/avx512f-pr101860.c: New test.
>
> --- gcc/config/i386/i386-expand.c.jj 2021-08-10 12:37:53.867159317 +0200
> +++ gcc/config/i386/i386-expand.c 2021-08-11 11:02:03.994908828 +0200
> @@ -18116,6 +18116,9 @@ ix86_expand_vec_one_operand_perm_avx512
> return false;
> }
>
> + if (d->testing_p)
> + return true;
> +
> target = d->target;
> op0 = d->op0;
> for (int i = 0; i < d->nelt; ++i)
> @@ -20481,6 +20484,10 @@ expand_vec_perm_broadcast_1 (struct expa
> gcc_assert (!TARGET_AVX2 || d->perm[0]);
> return false;
>
> + case E_V32HImode:
> + gcc_assert (!TARGET_AVX512BW);
> + return false;
> +
> default:
> gcc_unreachable ();
> }
> --- gcc/testsuite/gcc.target/i386/avx512f-pr101860.c.jj 2021-08-11 11:05:28.090072461 +0200
> +++ gcc/testsuite/gcc.target/i386/avx512f-pr101860.c 2021-08-11 11:05:17.157224399 +0200
> @@ -0,0 +1,5 @@
> +/* PR target/101860 */
> +/* { dg-do compile } */
> +/* { dg-options "-O2 -mavx512f -mno-avx512bw" } */
> +
> +#include "../../gcc.dg/torture/vshuf-v32hi.c"
>
> Jakub
>
--
BR,
Hongtao
prev parent reply other threads:[~2021-08-12 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 7:49 Jakub Jelinek
2021-08-12 8:52 ` Hongtao Liu [this message]
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='CAMZc-by00qZO=YsiOgj5w4ZOffdcHd2sS7dcK9LnKcbW3TG9Fw@mail.gmail.com' \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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: link
Be 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).