Loop bounds of affine.for didn't perform foldings like affine.load, affine.store.
Bound maps shall be more composed, leaving most affine.apply become dead.
This resolves the bug listed on https://bugs.llvm.org/show_bug.cgi?id=45203
Differential D99323
[mlir][affine] Fix unfolded bounding maps for affine.for eopXD on Mar 25 2021, 1:46 AM. Authored by
Details Loop bounds of affine.for didn't perform foldings like affine.load, affine.store. This resolves the bug listed on https://bugs.llvm.org/show_bug.cgi?id=45203
Diff Detail
Event TimelineThis comment was removed by eopXD. Comment Actions Thanks for improving this. A few comments.
Comment Actions Adjust testcase to include lower bound composition, Comment Actions Hi @bondhugula, CONFLICT (content): Merge conflict in libunwind/CMakeLists.txt CONFLICT (content): Merge conflict in libcxx/CMakeLists.txt Is this normal or how shall I do something different to rebase to main? Comment Actions A rebase leading to conflicts like these in unrelated files is indication that some developer/some process really messed up the LLVM git history upstream (@mehdi_amini @rriddle may have more insights here). In this case, what you'll have to do is to just cherry-pick your commit on the upstream main tip instead of rebasing. That will avoid all these conflicts completely unrelated to your PR. You will still see some conflicts on the affine ops files you are touching because you used a pretty old base - from at least a month ago. (Everyone using a significantly old base that traverses the time point where the history got messed up would see such conflcits while rebasing I believe.) Comment Actions [mlir][affine] Fix unfolded bounding maps for affine.for Loop bounds of affine.load didn’t perform foldings like affine.load, affine.store. This resolves the bug listed on https://bugs.llvm.org/show_bug.cgi?id=45203 |