aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/Object.cpp
diff options
context:
space:
mode:
authorAart Bik <ajcbik@google.com>2021-10-04 13:13:24 -0700
committerAart Bik <ajcbik@google.com>2021-10-05 09:35:59 -0700
commit16b8f4ddae1cb36ac16c6eb451613c032e4064f6 (patch)
treee36fc5e5d788004ce34eae0560cea40d907a2b5a /llvm/lib/Object/Object.cpp
parent7a4e9a0c73667cb80e4572d41535a9e48f1ed9ef (diff)
downloadllvm-16b8f4ddae1cb36ac16c6eb451613c032e4064f6.zip
llvm-16b8f4ddae1cb36ac16c6eb451613c032e4064f6.tar.gz
llvm-16b8f4ddae1cb36ac16c6eb451613c032e4064f6.tar.bz2
[mlir][sparse] add a "release" operation to sparse tensor dialect
We have several ways to materialize sparse tensors (new and convert) but no explicit operation to release the underlying sparse storage scheme at runtime (other than making an explicit delSparseTensor() library call). To simplify memory management, a sparse_tensor.release operation has been introduced that lowers to the runtime library call while keeping tensors, opague pointers, and memrefs transparent in the initial IR. *Note* There is obviously some tension between the concept of immutable tensors and memory management methods. This tension is addressed by simply stating that after the "release" call, no further memref related operations are allowed on the tensor value. We expect the design to evolve over time, however, and arrive at a more satisfactory view of tensors and buffers eventually. Bug: http://llvm.org/pr52046 Reviewed By: bixia Differential Revision: https://reviews.llvm.org/D111099
Diffstat (limited to 'llvm/lib/Object/Object.cpp')
0 files changed, 0 insertions, 0 deletions