llvm dev - Sep 2018 - Loop Distribution pass

On 09/13/2018 02:43 PM, Renato Golin via llvm-dev wrote:
> On Thu, 13 Sep 2018 at 18:46, Saito, Hideki <hideki.saito at
intel.com> wrote:
>> This all depends on those who are working on other loop xforms, since
we currently don't have bandwidth to drive that kind of changes into other
loop xforms. That's why when this line of questions pops up, I offer to work
together. Short of that, the best we can proactively do is to make vectorizer
analyses available outside of vectorizer (and easy to find). In some sense, this
is a chicken-egg problem. Once VPlan-based LV becomes good enough shape and if
this problem still remains, we could expand into working on vectorization
enabling transformations, but I really hope there are others who can work in
that area before us.
> I understand. We are working on more fundamental levels (register
> allocator, pipelining) before looking at the vectoriser, so it may
> take a while, too. Once we start looking at that, I'll let you know.
We should probably plan to chat about this at the dev meeting next
month. We'll have a few talks dealing with the future of our
loop-optimization infrastructure, and the transformations therein, and
this is also something that feeds into that discussion.

 -Hal
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-- 
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory

>We should probably plan to chat about this at the dev meeting next month.
I second the idea.

-----Original Message-----
From: Hal Finkel [mailto:hfinkel at anl.gov] 
Sent: Thursday, September 13, 2018 5:07 PM
To: Renato Golin <renato.golin at linaro.org>; Saito, Hideki
<hideki.saito at intel.com>
Cc: LLVM Dev <llvm-dev at lists.llvm.org>; Ulrich Weigand
<ulrich.weigand at de.ibm.com>
Subject: Re: [llvm-dev] Loop Distribution pass


On 09/13/2018 02:43 PM, Renato Golin via llvm-dev wrote:
> On Thu, 13 Sep 2018 at 18:46, Saito, Hideki <hideki.saito at
intel.com> wrote:
>> This all depends on those who are working on other loop xforms, since
we currently don't have bandwidth to drive that kind of changes into other
loop xforms. That's why when this line of questions pops up, I offer to work
together. Short of that, the best we can proactively do is to make vectorizer
analyses available outside of vectorizer (and easy to find). In some sense, this
is a chicken-egg problem. Once VPlan-based LV becomes good enough shape and if
this problem still remains, we could expand into working on vectorization
enabling transformations, but I really hope there are others who can work in
that area before us.
> I understand. We are working on more fundamental levels (register 
> allocator, pipelining) before looking at the vectoriser, so it may 
> take a while, too. Once we start looking at that, I'll let you know.
We should probably plan to chat about this at the dev meeting next month.
We'll have a few talks dealing with the future of our loop-optimization
infrastructure, and the transformations therein, and this is also something that
feeds into that discussion.

 -Hal
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
--
Hal Finkel
Lead, Compiler Technology and Programming Languages Leadership Computing
Facility Argonne National Laboratory

"Saito, Hideki via llvm-dev" <llvm-dev at lists.llvm.org>
writes:
>>We should probably plan to chat about this at the dev meeting next
month.
>
> I second the idea.
Count me in for that.  Is one of the BoFs amenable to this or should we
schedule some ad hoc thing?

                            -David