From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Evgeny Stupachenko <evstupac@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Richard Henderson <rth@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH 1/2, x86] Add palignr support for AVX2.
Date: Thu, 02 Oct 2014 06:30:00 -0000 [thread overview]
Message-ID: <CAFULd4bJ-8YcM_BFr-ZO_QhsV8Gbp0gJUbgfbKuguw9EmGCmUw@mail.gmail.com> (raw)
In-Reply-To: <20141001204358.GW1986@tucnak.redhat.com>
On Wed, Oct 1, 2014 at 10:43 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> > For PR62128, IMHO the right fix is attached. Note, this is again covered
> > in vshuf-*.c tests (test 22 in both vshuf-v32*.c and vshuf-v16*.c).
> > With that attached patch, pr62128.c (aka test_22 in vshuf-v32qi.c), changes:
> > - vpshufb .LC0(%rip), %ymm0, %ymm1
> > - vpshufb .LC1(%rip), %ymm0, %ymm0
> > - vpermq $78, %ymm1, %ymm1
> > - vpor %ymm1, %ymm0, %ymm0
> > + vpermq $78, %ymm0, %ymm1
> > + vpalignr $1, %ymm0, %ymm1, %ymm0
> > ret
> >
> > 2014-10-01 Jakub Jelinek <jakub@redhat.com>
> >
> > PR target/62128
> > * config/i386/i386.c (expand_vec_perm_1): Try expand_vec_perm_palignr
> > if it expands to a single insn only.
> > (expand_vec_perm_palignr): Add SINGLE_INSN_ONLY_P argument. If true,
> > fail unless in_order is true. Add forward declaration.
> > (expand_vec_perm_vperm2f128): Fix up comment about which permutation
> > is useful for one_operand_p.
> > (ix86_expand_vec_perm_const_1): Adjust expand_vec_perm_palignr caller.
>
> Now bootstrapped/regtested on x86_64-linux and i686-linux (and additionally
> tested also with --target_board=unix/-mavx2), ok for trunk?
>
OK.
Thanks,
Uros.
next prev parent reply other threads:[~2014-10-02 6:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 16:51 Evgeny Stupachenko
2014-04-28 17:29 ` H.J. Lu
2014-04-28 20:43 ` Evgeny Stupachenko
2014-04-28 18:15 ` Richard Henderson
2014-04-28 20:57 ` Evgeny Stupachenko
2014-04-28 21:08 ` Richard Henderson
2014-05-05 16:49 ` Evgeny Stupachenko
2014-05-19 10:42 ` Evgeny Stupachenko
2014-05-19 15:32 ` Richard Henderson
2014-07-03 9:53 ` Evgeny Stupachenko
2014-07-04 11:22 ` Uros Bizjak
2014-07-04 12:47 ` Evgeny Stupachenko
2014-07-07 14:40 ` Richard Henderson
2014-07-10 15:29 ` Evgeny Stupachenko
2014-08-14 8:09 ` Evgeny Stupachenko
2014-08-14 14:55 ` H.J. Lu
2014-08-26 12:59 ` Evgeny Stupachenko
2014-08-26 16:29 ` Richard Henderson
2014-08-27 15:50 ` Evgeny Stupachenko
2014-09-08 10:03 ` Evgeny Stupachenko
2014-09-16 13:15 ` Evgeny Stupachenko
2014-09-16 14:59 ` H.J. Lu
2014-09-17 13:01 ` Evgeny Stupachenko
2014-09-17 14:49 ` H.J. Lu
2014-09-17 17:26 ` Evgeny Stupachenko
2014-10-01 10:16 ` Evgeny Stupachenko
2014-10-01 10:28 ` Uros Bizjak
2014-10-01 10:35 ` Jakub Jelinek
2014-10-01 10:50 ` Evgeny Stupachenko
2014-10-01 11:38 ` Jakub Jelinek
2014-10-01 11:46 ` Uros Bizjak
2014-10-01 12:17 ` Jakub Jelinek
2014-10-01 12:25 ` Uros Bizjak
2014-10-01 12:56 ` Jakub Jelinek
2014-10-01 13:10 ` Uros Bizjak
2014-10-01 14:12 ` Jakub Jelinek
2014-10-01 14:21 ` Uros Bizjak
2014-10-01 20:44 ` Jakub Jelinek
2014-10-02 6:30 ` Uros Bizjak [this message]
2014-10-01 19:03 ` 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=CAFULd4bJ-8YcM_BFr-ZO_QhsV8Gbp0gJUbgfbKuguw9EmGCmUw@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=evstupac@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=rth@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).