From: Richard Biener <rguenther@suse.de>
To: Jeff Law <law@redhat.com>,Yuri Rumyantsev <ysrumyan@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,Ilya Enkovich
<enkovich.gnu@gmail.com>
Subject: Re: [PATCH, vec-tails] Support loop epilogue vectorization
Date: Sun, 06 Nov 2016 11:16:00 -0000 [thread overview]
Message-ID: <86385E0F-8619-4CD2-8032-E65ABBC5D855@suse.de> (raw)
In-Reply-To: <cf2393d5-55e5-a675-ea3b-7ffa2a57c6b3@redhat.com>
On November 5, 2016 3:40:04 AM GMT+01:00, Jeff Law <law@redhat.com> wrote:
>On 11/02/2016 06:27 AM, Richard Biener wrote:
>> I'm still torn about all the rest of the stuff and question its
>> usability (esp. merging the epilogue with the main vector loop).
>> But it has already been approved ... oh well.
>Note that merging of the epilogue with the main vector loop may well be
>
>useful for SVE as well. I'm hoping Richard S. will chime in on how to
>best exploit SVE.
Possibly, but full exploitation of SVE requires a full vectorizer rewrite. The only thing I can see us implementing is making the vector size fixed via versioning, that is, let the user specify -mvecsize=N and if that's not the case at runtime trap or execute a scalar variant.
Richard.
>Jeff
next prev parent reply other threads:[~2016-11-06 11:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 12:38 Yuri Rumyantsev
2016-11-02 12:27 ` Richard Biener
2016-11-03 12:33 ` Yuri Rumyantsev
2016-11-08 12:39 ` Richard Biener
2016-11-08 14:17 ` Yuri Rumyantsev
2016-11-10 12:34 ` Richard Biener
2016-11-10 12:36 ` Richard Biener
2016-11-11 11:15 ` Yuri Rumyantsev
2016-11-11 14:15 ` Yuri Rumyantsev
2016-11-11 14:43 ` Yuri Rumyantsev
2016-11-14 12:56 ` Richard Biener
2016-11-14 12:51 ` Richard Biener
2016-11-14 13:30 ` Yuri Rumyantsev
2016-11-14 13:41 ` Richard Biener
2016-11-14 15:39 ` Yuri Rumyantsev
2016-11-14 17:59 ` Richard Biener
2016-11-15 14:42 ` Yuri Rumyantsev
2016-11-16 9:56 ` Richard Biener
2016-11-18 13:20 ` Christophe Lyon
2016-11-18 15:46 ` Yuri Rumyantsev
2016-11-18 15:54 ` Christophe Lyon
2016-11-24 13:42 ` Yuri Rumyantsev
2016-11-28 14:39 ` Richard Biener
2016-11-28 16:57 ` Yuri Rumyantsev
2016-12-01 11:34 ` Richard Biener
2016-12-01 14:27 ` Yuri Rumyantsev
2016-12-01 14:46 ` Richard Biener
[not found] ` <CAEoMCqSkWgz+DJLe1M1CDxbk4LBtBU4r3rcVv7OcgpsGW4eTJA@mail.gmail.com>
[not found] ` <CAEoMCqRVVYTYWfhYrpi3TOuBe6XBw4ScVNstoqd8YShBsvRwMw@mail.gmail.com>
[not found] ` <CAEoMCqTdOHO_OxJ-5gxDJRPQDS+9kYkKd+WdgGJz8WMuUzD61A@mail.gmail.com>
[not found] ` <CAEoMCqQ5ZaT6TPbDL37DOZCEF5DHKWx995yn2fQZO3kV+vQ+EA@mail.gmail.com>
[not found] ` <CAEoMCqTCaRQU-mia98uX00CtpKA9w03fhaR2hXCdywXuVAQmSw@mail.gmail.com>
[not found] ` <CAEoMCqST8pOZmndKKuYWSyD=juPdGG1UAJ6NyAV3qkuxjV+3gA@mail.gmail.com>
[not found] ` <alpine.LSU.2.11.1612131455080.5294@t29.fhfr.qr>
2016-12-21 10:14 ` Yuri Rumyantsev
2016-12-21 17:23 ` Yuri Rumyantsev
2016-11-29 16:22 ` Christophe Lyon
2016-11-05 18:35 ` Jeff Law
2016-11-06 11:16 ` Richard Biener [this message]
2016-11-09 10:37 ` Bin.Cheng
2016-11-09 11:28 ` Yuri Rumyantsev
2016-11-09 11:46 ` Bin.Cheng
2016-11-09 12:12 ` Yuri Rumyantsev
2016-11-09 12:40 ` Bin.Cheng
2016-11-09 12:52 ` 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=86385E0F-8619-4CD2-8032-E65ABBC5D855@suse.de \
--to=rguenther@suse.de \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=ysrumyan@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).