public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Jeff Law <law@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"richard.sandiford@linaro.org" <richard.sandiford@linaro.org>,
	<nd@arm.com>
Subject: Re: Use single-iteration epilogues when peeling for gaps
Date: Sun, 07 Jan 2018 20:56:00 -0000	[thread overview]
Message-ID: <20180107205617.GM6993@arm.com> (raw)
In-Reply-To: <eff45e62-710a-6deb-0a41-1c72cf238286@redhat.com>

On Wed, Dec 13, 2017 at 04:42:02PM +0000, Jeff Law wrote:
> On 11/17/2017 08:38 AM, Richard Sandiford wrote:
> > This patch adds support for fully-masking loops that require peeling
> > for gaps.  It peels exactly one scalar iteration and uses the masked
> > loop to handle the rest.  Previously we would fall back on using a
> > standard unmasked loop instead.
> > 
> > Tested on aarch64-linux-gnu (with and without SVE), x86_64-linux-gnu
> > and powerpc64le-linux-gnu.  OK to install?
> > 
> > Richard
> > 
> > 
> > 2017-11-17  Richard Sandiford  <richard.sandiford@linaro.org>
> > 	    Alan Hayward  <alan.hayward@arm.com>
> > 	    David Sherwood  <david.sherwood@arm.com>
> > 
> > gcc/
> > 	* tree-vect-loop-manip.c (vect_gen_scalar_loop_niters): Replace
> > 	vfm1 with a bound_epilog parameter.
> > 	(vect_do_peeling): Update calls accordingly, and move the prologue
> > 	call earlier in the function.  Treat the base bound_epilog as 0 for
> > 	fully-masked loops and retain vf - 1 for other loops.  Add 1 to
> > 	this base when peeling for gaps.
> > 	* tree-vect-loop.c (vect_analyze_loop_2): Allow peeling for gaps
> > 	with fully-masked loops.
> > 	(vect_estimate_min_profitable_iters): Handle the single peeled
> > 	iteration in that case.
> > 
> > gcc/testsuite/
> > 	* gcc.target/aarch64/sve_struct_vect_18.c: Check the number
> > 	of branches.
> > 	* gcc.target/aarch64/sve_struct_vect_19.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_20.c: New test.
> > 	* gcc.target/aarch64/sve_struct_vect_20_run.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_21.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_21_run.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_22.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_22_run.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_23.c: Likewise.
> > 	* gcc.target/aarch64/sve_struct_vect_23_run.c: Likewise.
> OK.
> jeff

The AArch64 tests are OK.

Thanks,
James

      reply	other threads:[~2018-01-07 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 15:46 Richard Sandiford
2017-12-13 16:42 ` Jeff Law
2018-01-07 20:56   ` James Greenhalgh [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=20180107205617.GM6993@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=nd@arm.com \
    --cc=richard.sandiford@linaro.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).