From: Marc Glisse <marc.glisse@inria.fr>
To: gcc-patches@gcc.gnu.org
Cc: rdsandiford@googlemail.com
Subject: Re: [rtl, i386] combine concat+permutation
Date: Fri, 17 Aug 2012 10:43:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1208171240240.3292@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <alpine.DEB.2.02.1208032224080.12269@stedding.saclay.inria.fr>
Ping
http://gcc.gnu.org/ml/gcc-patches/2012-08/msg00205.html
(Cc: the nice reviewer of the previous patch)
On Fri, 3 Aug 2012, Marc Glisse wrote:
> Hello,
>
> this is a follow up to the patch applied after this discussion:
> http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00504.html
>
> It handles the -mavx __builtin_shuffle case mentioned there.
>
> It passes bootstrap (languages=c,c++) and regtest on x86_64.
>
>
> 2012-08-04 Marc Glisse <marc.glisse@inria.fr>
>
> gcc/
> * simplify-rtx.c (simplify_binary_operation_1): Optimize shuffle of
> a concatenation.
>
> gcc/testsuite/
> * gcc.target/i386/perm-concat.c: New test.
--
Marc Glisse
next prev parent reply other threads:[~2012-08-17 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 20:47 Marc Glisse
2012-08-17 10:43 ` Marc Glisse [this message]
2012-08-17 10:54 ` Jakub Jelinek
2012-08-18 15:03 ` Marc Glisse
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=alpine.DEB.2.02.1208171240240.3292@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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).