From: Yuri Rumyantsev <ysrumyan@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Ilya Enkovich <enkovich.gnu@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>, Jeff Law <law@redhat.com>,
Igor Zamyatin <izamyatin@gmail.com>
Subject: Re: [RFC] Combine vectorized loops with its scalar remainder.
Date: Mon, 23 Nov 2015 15:54:00 -0000 [thread overview]
Message-ID: <CAEoMCqTMy6wW3=ABeEJTow0wsFWYJk2u=1rm3eBAvUuZ+-Q4Eg@mail.gmail.com> (raw)
In-Reply-To: <CAEoMCqTuiFXv-y-SUbHn1ke__OKzCOpynjxhYYYbN6Smph5szQ@mail.gmail.com>
Hi Richard,
Did you have a chance to look at this?
Thanks.
Yuri.
2015-11-13 13:35 GMT+03:00 Yuri Rumyantsev <ysrumyan@gmail.com>:
> Hi Richard,
>
> Here is updated version of the patch which 91) is in sync with trunk
> compiler and (2) contains simple cost model to estimate profitability
> of scalar epilogue elimination. The part related to vectorization of
> loops with small trip count is in process of developing. Note that
> implemented cost model was not tuned well for HASWELL and KNL but we
> got ~6% speed-up on 436.cactusADM from spec2006 suite for HASWELL.
>
> 2015-11-10 17:52 GMT+03:00 Richard Biener <richard.guenther@gmail.com>:
>> On Tue, Nov 10, 2015 at 2:02 PM, Ilya Enkovich <enkovich.gnu@gmail.com> wrote:
>>> 2015-11-10 15:30 GMT+03:00 Richard Biener <richard.guenther@gmail.com>:
>>>> On Tue, Nov 3, 2015 at 1:08 PM, Yuri Rumyantsev <ysrumyan@gmail.com> wrote:
>>>>> Richard,
>>>>>
>>>>> It looks like misunderstanding - we assume that for GCCv6 the simple
>>>>> scheme of remainder will be used through introducing new IV :
>>>>> https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01435.html
>>>>>
>>>>> Is it true or we missed something?
>>>>
>>>> <quote>
>>>>> > Do you have an idea how "masking" is better be organized to be usable
>>>>> > for both 4b and 4c?
>>>>>
>>>>> Do 2a ...
>>>> Okay.
>>>> </quote>
>>>
>>> 2a was 'transform already vectorized loop as a separate
>>> post-processing'. Isn't it what this prototype patch implements?
>>> Current version only masks loop body which is in practice applicable
>>> for AVX-512 only in the most cases. With AVX-512 it's easier to see
>>> how profitable masking might be and it is a main target for the first
>>> masking version. Extending it to prologues/epilogues and thus making
>>> it more profitable for other targets is the next step and is out of
>>> the scope of this patch.
>>
>> Ok, technically the prototype transforms the already vectorized loop.
>> Of course I meant the vectorized loop be copied, masked and that
>> result used as epilogue...
>>
>> I'll queue a more detailed look into the patch for this week.
>>
>> Did you perform any measurements with this patch like # of
>> masked epilogues in SPEC 2006 FP (and any speedup?)
>>
>> Thanks,
>> Richard.
>>
>>> Thanks,
>>> Ilya
>>>
>>>>
>>>> Richard.
>>>>
next prev parent reply other threads:[~2015-11-23 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 10:57 Yuri Rumyantsev
2015-11-03 10:08 ` Richard Henderson
2015-11-03 10:35 ` Yuri Rumyantsev
2015-11-03 11:47 ` Richard Biener
2015-11-03 12:08 ` Yuri Rumyantsev
2015-11-10 12:30 ` Richard Biener
2015-11-10 13:02 ` Ilya Enkovich
2015-11-10 14:52 ` Richard Biener
2015-11-13 10:36 ` Yuri Rumyantsev
2015-11-23 15:54 ` Yuri Rumyantsev [this message]
2015-11-24 9:21 ` Richard Biener
2015-11-27 13:49 ` Richard Biener
2015-11-30 15:04 ` Yuri Rumyantsev
2015-12-15 16:41 ` Yuri Rumyantsev
2016-01-11 10:07 ` Yuri Rumyantsev
2016-02-09 16:10 ` Ilya Enkovich
2016-02-09 16:18 ` Jeff Law
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='CAEoMCqTMy6wW3=ABeEJTow0wsFWYJk2u=1rm3eBAvUuZ+-Q4Eg@mail.gmail.com' \
--to=ysrumyan@gmail.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=izamyatin@gmail.com \
--cc=law@redhat.com \
--cc=richard.guenther@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).