[mlir][bufferization][WIP] Use BufferOriginAnalysis
to fold away dealloc
runtime checks
#79602
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds the
BufferOriginAnalysis
, which can be queried by the buffer deallocation pass to check if two buffers originate from the same allocation.This analysis enables additional simplifications during
-buffer-deallocation-simplification
. In particular, "regular"scf.for
loop nests, that yield buffers (or reallocations thereof) in the same order as they appear in theiter_args
, are now handled much more efficiently. (TODO: Add test case.) Such IR patterns are generated by the sparse compiler.Depends on #78718. Review only the top commit.