From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Liu, Hongtao" <hongtao.liu@intel.com>
Subject: RE: [PATCH v3] i386: Disable ix86_expand_vecop_qihi2 when !TARGET_AVX512BW
Date: Wed, 22 May 2024 02:21:35 +0000 [thread overview]
Message-ID: <SA1PR11MB59467A3DF62385526C6443D9ECEB2@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAFULd4ZpBWGqoFJviKaMAWHeisPmq12n_dK9imxo+EkuEYhfDg@mail.gmail.com>
> -----Original Message-----
> From: Uros Bizjak <ubizjak@gmail.com>
> Sent: Tuesday, May 21, 2024 9:04 PM
> To: Jiang, Haochen <haochen.jiang@intel.com>
> Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao <hongtao.liu@intel.com>
> Subject: Re: [PATCH v3] i386: Disable ix86_expand_vecop_qihi2
> when !TARGET_AVX512BW
>
> On Tue, May 21, 2024 at 11:01 AM Haochen Jiang
> <haochen.jiang@intel.com> wrote:
> >
> > Hi all,
> >
> > This is the v3 patch to fix PR115069. The new testcase has passed.
> >
> > Changes in v3:
> > - Simplify the testcase.
> >
> > Changes in v2:
> > - Add a testcase.
> > - Change the comment for the early exit.
> >
> > Thx,
> > Haochen
> >
> > Since vpermq is really slow, we should avoid using it for permutation
> > when vpmovwb is not available (needs AVX512BW) for
> ix86_expand_vecop_qihi2
> > and fall back to ix86_expand_vecop_qihi.
> >
> > gcc/ChangeLog:
> >
> > PR target/115069
> > * config/i386/i386-expand.cc (ix86_expand_vecop_qihi2):
> > Do not enable the optimization when AVX512BW is not enabled.
> >
> > gcc/testsuite/ChangeLog:
> >
> > PR target/115069
> > * gcc.target/i386/pr115069.c: New.
>
> LGTM, with a nit below.
Ok and I will also backport the patch to GCC14.
Thx,
Haochen
>
> Thanks,
> Uros.
prev parent reply other threads:[~2024-05-22 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 6:16 [PATCH] " Haochen Jiang
2024-05-21 6:17 ` Hongtao Liu
2024-05-21 6:35 ` Uros Bizjak
2024-05-21 7:13 ` [PATCH v2] " Haochen Jiang
2024-05-21 7:21 ` Hongtao Liu
2024-05-21 8:36 ` Jiang, Haochen
2024-05-21 9:01 ` [PATCH v3] " Haochen Jiang
2024-05-21 13:04 ` Uros Bizjak
2024-05-22 2:21 ` Jiang, Haochen [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=SA1PR11MB59467A3DF62385526C6443D9ECEB2@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=ubizjak@gmail.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).