Clarify that sparse_tensor.foreach iterates sparse_tensor in stored dim order.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td | ||
---|---|---|
850 | I would say that the "loop iterates over the stored elements in the storage order" or something like htat (since stored dimension order still implies some order, but for unsorted versions, all is lost and add: No matter what storage order is used, however, the indices passed to the block always obey the original dimension order. |
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td | ||
---|---|---|
850 |
+1. "Stored dimension order" will become more and more of a misnomer as we start adding support for more unique sparsity formats. (E.g., the storage levels of formats like DIA don't really have anything to do with "dimensions" anymore)
+1. That's very well phrased |
I would say that the "loop iterates over the stored elements in the storage order" or something like htat (since stored dimension order still implies some order, but for unsorted versions, all is lost
and add:
No matter what storage order is used, however, the indices passed to the block always obey the original dimension order.