[PATCH] D14715: [Polly] Loop versioning after code generation (WIP)

[Johannes Doerfert via llvm-commits]

Polly has to become a SCC pass anyway in order to make parallelization
valid (and allow inter-procedural analysis), thus this should not be a
concern. However, it seems odd and expensive to create a function only
to inline it again, so we might not want to do that.

On 12/14, Michael Kruse via llvm-commits wrote:
> Meinersbur added a comment.
> 
> In http://reviews.llvm.org/D14715#309767, @llvm-commits wrote:
> 
> > To bad, I thought this was a nice solution.
> >
> > One of the students I advice currently tackles a similar problem when SE
> >  is used to synthesise code in a parallel subfunction... I'll let you
> >  know once we figured that out.
> 
> 
> One of my other suggestions was to generate the code in a separate function which is to be inlined by LLVM afterwards. Unfortunatelt it is forbidden for function passes to touch (or create) functions they were not invoked on.
> 
> 
> http://reviews.llvm.org/D14715
> 
> 
> 
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits

-- 

Johannes Doerfert
Researcher / PhD Student

Compiler Design Lab (Prof. Hack)
Saarland University, Computer Science
Building E1.3, Room 4.31

Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de
Fax. +49 (0)681 302-3065  : http://www.cdl.uni-saarland.de/people/doerfert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20151214/d9ebdaaa/attachment.sig>