[PATCH] D35761: [Polly][WIP] Use SCEV information for the second level aliasing

[Tobias Grosser via Phabricator via llvm-commits]

grosser added a comment.

Hi Roman,

thanks for the patch. I looked into it a couple of times, but need to have another deeper look. Two high-level questions already:

1. Why do we need to use SCEV? Should we not be able to tell form our information which base pointers are expected to be identical?
2. What exactly must be checked in the new test case here. What was generated before, why was this wrong, and what does the new code generate.

Also, I may have missed this earlier. Why are the number of elements in the check lines growing so much. Is this expected?

CHECK-NEXT: !43 = !{!3, !4, !0, !6, !7, !11, !14, !16, !18, !20, !22, !24, !26, !28, !30, !32, !34, !36, !38, !40}


https://reviews.llvm.org/D35761