From: Kirill Yukhin <kirill.yukhin@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] vec_extract XMM16-XMM17 improvements
Date: Thu, 12 May 2016 08:22:00 -0000 [thread overview]
Message-ID: <20160512082125.GF4018@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <20160512081137.GU28550@tucnak.redhat.com>
On 12 May 10:11, Jakub Jelinek wrote:
> On Thu, May 12, 2016 at 10:30:53AM +0300, Kirill Yukhin wrote:
> > Hi,
> > On 09 May 18:55, Jakub Jelinek wrote:
> > > Hi!
> > >
> > > vpextr{b,w} are in AVX512BW, so is vpsrldq, and vpextr{d,q} are in
> > > AVX512DQ.
> > >
> > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
> > OK.
>
> Note, this patch depends on the
> https://gcc.gnu.org/ml/gcc-patches/2016-05/msg00393.html
> patch. You've acked an earlier version of that patch, but not
> the one with the new constraint.
> Is that also ok for trunk?
Yes.
>
> > > 2016-05-09 Jakub Jelinek <jakub@redhat.com>
> > >
> > > * config/i386/i386.md (isa): Add x64_avx512dq, enable if
> > > TARGET_64BIT && TARGET_AVX512DQ.
> > > * config/i386/sse.md (*vec_extract<mode>): Add avx512bw alternatives.
> > > (*vec_extract<PEXTR_MODE12:mode>_zext): Add avx512bw alternative.
> > > (*vec_extract<ssevecmodelower>_0, *vec_extractv4si_0_zext,
> > > *vec_extractv2di_0_sse): Use v constraint instead of x constraint.
> > > (*vec_extractv4si): Add avx512dq and avx512bw alternatives.
> > > (*vec_extractv4si_zext): Add avx512dq alternative.
> > > (*vec_extractv2di_1): Add x64_avx512dq and avx512bw alternatives,
> > > use v instead of x constraint in other alternatives where possible.
> > >
> > > * gcc.target/i386/avx512bw-vpextr-1.c: New test.
> > > * gcc.target/i386/avx512dq-vpextr-1.c: New test.
>
> Jakub
prev parent reply other threads:[~2016-05-12 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:55 Jakub Jelinek
2016-05-12 7:32 ` Kirill Yukhin
2016-05-12 8:11 ` Jakub Jelinek
2016-05-12 8:22 ` Kirill Yukhin [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=20160512082125.GF4018@msticlxl57.ims.intel.com \
--to=kirill.yukhin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).