[polly] r270409 - [FIX] Let ScalarEvolution forget hoisted values

[Johannes Doerfert via llvm-commits]

On 06/07, Tobias Grosser wrote:
> On 05/23/2016 11:02 AM, Johannes Doerfert via llvm-commits wrote:
> > Author: jdoerfert
> > Date: Mon May 23 04:02:54 2016
> > New Revision: 270409
> > 
> > URL: http://llvm.org/viewvc/llvm-project?rev=270409&view=rev
> > Log:
> > [FIX] Let ScalarEvolution forget hoisted values
> > 
> >   We have to rethink the handling of escaping values in order to make
> >   this kind of "fixes" go away.
> 
> CCing Utpal.
> 
> This is one of the reasons why a function level Polly that first builds
> up all scops and then code-generates them one by one is problematic. If
> this value is now used in the other SCoP, we may (or may not?) get into
> trouble. As you are working towards this goal, it will be good to keep
> this in mind.
The problem is that we use a caching ScalarEvolution (or ScalarEvolution
int the first place). Your argument doesn't really apply as we see such
problems __even though__ we do not build all SCoPs first. We might have
some of them with a function level Polly but we have them now too.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: Digital signature
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160608/dbc927b8/attachment-0001.sig>