Reading from tensor.empty or bufferization.alloc_tensor (without copy) cannot cause a conflict because these ops do not specify the contents of their result tensors.
Depends On: D143181
Paths
| Differential D143183
[mlir][bufferization] Reads from tensors with undefined data are not a conflict ClosedPublic Authored by springerm on Feb 2 2023, 6:57 AM.
Details Summary Reading from tensor.empty or bufferization.alloc_tensor (without copy) cannot cause a conflict because these ops do not specify the contents of their result tensors. Depends On: D143181
Diff Detail
Event Timelinespringerm mentioned this in D143087: [mlir][bufferization] Fix bufferization of repetitive regions.Feb 2 2023, 7:25 AM springerm added a child revision: D143087: [mlir][bufferization] Fix bufferization of repetitive regions.
This revision is now accepted and ready to land.Feb 6 2023, 7:01 AM Closed by commit rG1fdf06d6d79e: [mlir][bufferization] Reads from tensors with undefined data are not a conflict (authored by springerm). · Explain WhyFeb 6 2023, 7:16 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 495120 mlir/include/mlir/Dialect/Bufferization/IR/BufferizableOpInterface.h
mlir/lib/Dialect/Bufferization/IR/BufferizableOpInterface.cpp
mlir/lib/Dialect/Bufferization/Transforms/OneShotAnalysis.cpp
mlir/test/Dialect/Bufferization/Transforms/one-shot-bufferize-analysis.mlir
mlir/test/Dialect/SCF/one-shot-bufferize.mlir
|
Can we please add a test case also for bufferization.alloc_tensor?