From: Richard Biener <rguenther@suse.de>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Lift restrictions on SLP permutation for loop vect
Date: Thu, 11 Jun 2015 14:20:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1506111608220.14687@zhemvz.fhfr.qr> (raw)
In-Reply-To: <CAFULd4bcKGtRCJJMypeweT-UeqsnFfQkVTOyO+uK6Eqch_3ghg@mail.gmail.com>
On Thu, 11 Jun 2015, Uros Bizjak wrote:
> > So this turned up other issues thus the following is what I have
> > committed after bootstrapping and testing on x86_64-unknown-linux-gnu.
> >
> > Richard.
> >
> > 2015-06-08 Richard Biener <rguenther@suse.de>
> >
> > * tree-vect-stmts.c (vectorizable_load): Compute the pointer
> > adjustment for gaps at the end of a SLP load group properly.
> > * tree-vect-slp.c (vect_supported_load_permutation_p): Allow
> > all permutations we can generate.
> > (vect_transform_slp_perm_load): Use the correct group-size.
> >
> > * gcc.dg/vect/slp-perm-10.c: New testcase.
> > * gcc.dg/vect/slp-23.c: Adjust.
> > * gcc.dg/torture/pr53366-2.c: Also verify cross-iteration vector pointer update.
>
> This patch caused:
>
> FAIL: gcc.target/i386/pr61403.c scan-assembler blend
Yeah, I noticed. We now want to vectorize this differently but
fail due to the cost model. I'm working on enhancing the vectorizer
here.
Richard.
next prev parent reply other threads:[~2015-06-11 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 14:09 Uros Bizjak
2015-06-11 14:20 ` Richard Biener [this message]
2015-06-11 14:23 ` James Greenhalgh
2015-06-11 14:30 ` Richard Biener
2015-06-11 14:34 ` James Greenhalgh
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 12:01 Richard Biener
2015-06-08 13:03 ` Richard Biener
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.LSU.2.11.1506111608220.14687@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--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).