From: Richard Biener <rguenther@suse.de>
To: Alan Lawrence <alan.lawrence@arm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR68559
Date: Wed, 02 Dec 2015 13:31:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1512021430400.4884@t29.fhfr.qr> (raw)
In-Reply-To: <565EF1DB.2070808@arm.com>
On Wed, 2 Dec 2015, Alan Lawrence wrote:
> On 27/11/15 14:13, Richard Biener wrote:
> >
> > The following fixes the excessive peeling for gaps we do when doing
> > SLP now that I removed most of the restrictions on having gaps in
> > the first place.
> >
> > This should make low-trip vectorized loops more efficient (sth
> > also the combine-epilogue-with-vectorized-body-by-masking patches
> > claim to do).
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
> >
> > Richard.
> >
> > 2015-11-27 Richard Biener <rguenther@suse.de>
> >
> > PR tree-optimization/68559
> > * tree-vect-data-refs.c (vect_analyze_group_access_1): Move
> > peeling for gap checks ...
> > * tree-vect-stmts.c (vectorizable_load): ... here and relax
> > for SLP.
> > * tree-vect-loop.c (vect_analyze_loop_2): Re-set
> > LOOP_VINFO_PEELING_FOR_GAPS before re-trying without SLP.
> >
> > * gcc.dg/vect/slp-perm-4.c: Adjust again.
> > * gcc.dg/vect/pr45752.c: Likewise.
>
> Since this, we have
>
> FAIL: gcc.dg/vect/pr45752.c -flto -ffat-lto-objects scan-tree-dump-times vect
> "gaps requires scalar epilogue loop" 0
> FAIL: gcc.dg/vect/pr45752.c scan-tree-dump-times vect "gaps requires scalar
> epilogue loop" 0
>
> on aarch64 platforms (aarch64-none-linux-gnu, aarch64-none-elf,
> aarch64_be-none-elf).
Can you open a bug and attach -details vectorizer dumps?
Richard.
prev parent reply other threads:[~2015-12-02 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 14:21 Richard Biener
2015-12-02 13:28 ` Alan Lawrence
2015-12-02 13:31 ` Richard Biener [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=alpine.LSU.2.11.1512021430400.4884@t29.fhfr.qr \
--to=rguenther@suse.de \
--cc=alan.lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).