diff options
| author | Matthias Springer <me@m-sp.org> | 2023-06-27 14:29:18 +0200 |
|---|---|---|
| committer | Matthias Springer <me@m-sp.org> | 2023-06-27 14:57:13 +0200 |
| commit | d31a6dfbc0a9b259e365b3748bf142884b6fabe5 (patch) | |
| tree | d331b0c10541fe7417d9c5e53351437a4b2d8f95 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
| parent | 03301be0baf7f8a4e0169b4d68dffd8b61b229e1 (diff) | |
[mlir][bufferization] Add bufferization.copy_tensor op
This operation is a "copy" operation on tensors. It is guaranteed to bufferize to a memcpy. This is different from "tensor.insert_slice", which may fold away.
Note: There is a symmetry between certain tensor, bufferization and memref ops:
* `tensor.empty`, `bufferization.alloc_tensor`, `memref.alloc`
* (none), `bufferization.dealloc_tensor`, `memref.dealloc`
* `tensor.insert_slice`, `bufferization.copy_tensor`, `memref.copy`
Tensor ops can generally canonicalize/fold away, while bufferization dialect ops can be used when a certain side effect is expected to materialize; so they do not fold away.
Differential Revision: https://reviews.llvm.org/D153552
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions