All bufferizable ops that bufferize to an allocation receive a bufferization.escape attribute during TensorCopyInsertion.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/include/mlir/Dialect/Bufferization/IR/BufferizableOpInterface.td | ||
---|---|---|
23 | did you really intent, "may bufferize to", or will "bufferizes to" be better? | |
mlir/include/mlir/Dialect/Bufferization/IR/BufferizationBase.td | ||
43 | perhaps add one more sentence on clarifying "escape", for example which means the buffer needs to be allocated outside this method or which means the allocation "escape" the scope of the method to the caller (or something like that | |
mlir/lib/Dialect/Bufferization/Transforms/TensorCopyInsertion.cpp | ||
80 | Can't we use this condition to guard the whole analysis? |
mlir/include/mlir/Dialect/Bufferization/IR/BufferizableOpInterface.td | ||
---|---|---|
23 | Yes, this is on purpose. Sometimes we don't know what's going to happen at runtime. Then we should return true here. Extended the comment. |
did you really intent, "may bufferize to", or will "bufferizes to" be better?