[Polly] Generating code for changed memory accesses

'Johannes Doerfert' doerfert at cs.uni-saarland.de
Tue Jul 29 01:03:28 PDT 2014


> I don't see why removing the tuple name should be needed. The tuple names
> should match. If they don't either I misunderstood something or you use them
> in the wrong way.
That's because I did something else (and had still the same idea in mind).
With the reverse relation and pullback we don't need that anymore.

> Sorry, I forgot to reverse the schedule map: Here the full flow for your
That helps me, and the fact that I now understand the *_pullback_* functions.

My first approach used the Stmt scattering which I applied with
isl_map_apply_domain, but thats different from what _pullback_ does.

I will come up with new patch (hopefully) tomorrow and integrate also your other
comments. However, I would like to enable this kind of codegen for all access
relations (not only imported ones) as long as delinearization is off and the
memory access is not "non-affine/overaproximated".
Is that OK with you or do you disagree?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140729/626bc669/attachment.sig>


More information about the llvm-commits mailing list