diff --git a/mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td b/mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td --- a/mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td +++ b/mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td @@ -181,9 +181,9 @@ Inserts the given value at given indices into the underlying sparse storage format of the given tensor with the given indices. This operation can only be applied when a tensor materializes unintialized - with an `init` operation, the insertions occur in strict lexicographical - index order, and the final tensor is constructed with a `tensor` - operation that has the `hasInserts` attribute set. + with an `bufferization.alloc_tensor` operation, the insertions occur in + strict lexicographical index order, and the final tensor is constructed + with a `load` operation that has the `hasInserts` attribute set. Note that this operation is "impure" in the sense that its behavior is solely defined by side-effects and not SSA values. The semantics @@ -314,12 +314,12 @@ string summary = "Releases underlying sparse storage format of given tensor"; string description = [{ Releases the underlying sparse storage format for a tensor that - materialized earlier through a `new` operator, `init` operator, or a - `convert` operator with an annotated tensor type as destination (unless - that convert is folded away since the source and destination types were - identical). This operation should only be called once for any materialized - tensor. Also, after this operation, any subsequent `memref` querying - operation on the tensor returns undefined results. + materialized earlier through a `new` operation, a `convert` operation + with annotated destination tensor type (unless the convert is folded + away), or a `bufferization.alloc_tensor` operation. The release operation + should only be called once for any materialized tensor. After this + operation, any subsequent `memref` querying operation on the tensor + returns undefined results. Note that this operation is "impure" in the sense that its behavior is solely defined by side-effects and not SSA values. The semantics