[Mlir-commits] [mlir] [mlir][affine] Avoid fusion when the sibling loop has result usage (PR #216564)
Kunal Dubey
llvmlistbot at llvm.org
Thu Aug 27 05:09:51 PDT 2026
xakep8 wrote:
> Instead of refusing fusion, we can carry over the results of the sibling loop into the target loop and update the users accordingly.
Yes I have considered that remapping but it would be a bigger change so I had suggested
> We could just reject the fusion for now and I can raise another PR for the remapping as I think that would take a lot of handling of iter_args/results in the destination loop.
[here](https://github.com/llvm/llvm-project/issues/216464#issuecomment-5306027159) should I continue the remapping this PR?
https://github.com/llvm/llvm-project/pull/216564
More information about the Mlir-commits
mailing list