From: Hongtao Liu <crazylht@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Kirill Yukhin <kirill.yukhin@gmail.com>
Subject: Re: [PATCH] [PR target/97194] [AVX2] Support variable index vec_set.
Date: Thu, 26 Nov 2020 09:45:33 +0800 [thread overview]
Message-ID: <CAMZc-byUNwXa5+Z7JARa+qqwKRdtQETfFb5J9RR_VNNv6dJXzg@mail.gmail.com> (raw)
In-Reply-To: <48a0071d-e909-3b10-d61f-c23d12dc8b89@redhat.com>
Thanks for the review.
BTW, the patch is already installed because uros helped to review this
patch in another thread
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/558682.html
On Thu, Nov 26, 2020 at 3:15 AM Jeff Law <law@redhat.com> wrote:
>
>
>
> On 11/11/20 1:03 AM, Hongtao Liu via Gcc-patches wrote:
>
> >
> >
> >
> > vec_set_rebaserebase_onr11-4901.patch
> >
> > From c9d684c37b5f79f68f938f39eeb9e7989b10302d Mon Sep 17 00:00:00 2001
> > From: liuhongt <hongtao.liu@intel.com>
> > Date: Mon, 19 Oct 2020 16:04:39 +0800
> > Subject: [PATCH] Support variable index vec_set.
> >
> > gcc/ChangeLog:
> >
> > PR target/97194
> > * config/i386/i386-expand.c (ix86_expand_vector_set_var): New function.
> > * config/i386/i386-protos.h (ix86_expand_vector_set_var): New Decl.
> > * config/i386/predicates.md (vec_setm_operand): New predicate,
> > true for const_int_operand or register_operand under TARGET_AVX2.
> > * config/i386/sse.md (vec_set<mode>): Support both constant
> > and variable index vec_set.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/i386/avx2-vec-set-1.c: New test.
> > * gcc.target/i386/avx2-vec-set-2.c: New test.
> > * gcc.target/i386/avx512bw-vec-set-1.c: New test.
> > * gcc.target/i386/avx512bw-vec-set-2.c: New test.
> > * gcc.target/i386/avx512f-vec-set-2.c: New test.
> > * gcc.target/i386/avx512vl-vec-set-2.c: New test.
> This is OK. Sorry for the delays.
>
> jeff
>
--
BR,
Hongtao
next prev parent reply other threads:[~2020-11-26 1:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 8:23 Hongtao Liu
2020-10-19 9:07 ` Richard Biener
2020-10-19 9:39 ` Hongtao Liu
2020-10-19 9:55 ` Richard Biener
2020-10-20 2:37 ` Hongtao Liu
2020-10-20 7:36 ` Richard Biener
2020-10-27 7:51 ` Hongtao Liu
2020-11-11 8:03 ` Hongtao Liu
2020-11-25 19:15 ` Jeff Law
2020-11-26 1:45 ` Hongtao Liu [this message]
2020-11-11 8:45 Uros Bizjak
2020-11-12 2:06 ` Hongtao Liu
2020-11-12 8:20 ` Uros Bizjak
2020-11-12 9:12 ` Hongtao Liu
2020-11-12 9:15 ` Hongtao Liu
2020-11-12 9:25 ` Hongtao Liu
2020-11-12 13:59 ` Richard Biener
2020-11-12 17:51 ` Uros Bizjak
2020-11-12 18:26 ` Uros Bizjak
2020-11-12 18:34 ` Uros Bizjak
2020-11-16 11:57 ` Uros Bizjak
2020-11-19 10:54 ` Richard Sandiford
2020-11-16 10:16 ` Uros Bizjak
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-byUNwXa5+Z7JARa+qqwKRdtQETfFb5J9RR_VNNv6dJXzg@mail.gmail.com \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kirill.yukhin@gmail.com \
--cc=law@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).