From: Jeff Law <law@redhat.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC][PATCH, vec-tails 00/10] Support vectorization of loop epilogues
Date: Thu, 16 Jun 2016 06:28:00 -0000 [thread overview]
Message-ID: <6abacb08-f419-5583-b102-1128bab4c794@redhat.com> (raw)
In-Reply-To: <20160519193515.GA40563@msticlxl57.ims.intel.com>
On 05/19/2016 01:35 PM, Ilya Enkovich wrote:
> Hi,
>
> This series is an extension of previous work on loop epilogue combining [1].
>
> It introduces three ways to handle vectorized loop epilogues: combine it with
> vectorized loop, vectorize it with masks, vectorize it using a smaller vector
> size.
>
> Also it supports vectorization of loops with low trip count.
[ ... ]
So now that I'm working through the patches the one obvious thing that
is missing is testcases... We should have tests for all the new
capabilities. It's probably advisable to have some tests for cases
where the costing models say "don't vectorize the epilogue" as well.
Jeff
prev parent reply other threads:[~2016-06-16 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 19:36 Ilya Enkovich
2016-06-15 12:06 ` Richard Biener
2016-06-16 4:14 ` Jeff Law
2016-06-16 6:28 ` Jeff Law [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=6abacb08-f419-5583-b102-1128bab4c794@redhat.com \
--to=law@redhat.com \
--cc=enkovich.gnu@gmail.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).