4 Commits

Author	SHA1	Message	Date
Aart Bik	dc4cfdbb8f	[mlir][sparse] provide an AoS "view" into sparse runtime support lib (#87116) ... Note that even though the sparse runtime support lib always uses SoA storage for COO storage (and provides correct codegen by means of views into this storage), in some rare cases we need the true physical SoA storage as a coordinate buffer. This PR provides that functionality by means of a (costly) coordinate buffer call. Since this is currently only used for testing/debugging by means of the sparse_tensor.print method, this solution is acceptable. If we ever want a performing version of this, we should truly support AoS storage of COO in addition to the SoA used right now.	2024-03-29 15:30:36 -07:00
Aart Bik	691fc7cdcc	[mlir][sparse] add dim/lvl information to sparse_tensor.print (#83913) ... More information is more testing! Also adjusts already migrated integration tests	2024-03-04 14:32:49 -08:00
Aart Bik	8394ec9ff1	[mlir][sparse] add a few more cases to sparse_tensor.print test (#83338)	2024-02-28 14:05:40 -08:00
Aart Bik	d37affb06f	[mlir][sparse] add a sparse_tensor.print operation (#83321) ... This operation is mainly used for testing and debugging purposes but provides a very convenient way to quickly inspect the contents of a sparse tensor (all components over all stored levels). Example: [ [ 1, 0, 2, 0, 0, 0, 0, 0 ], [ 0, 0, 0, 0, 0, 0, 0, 0 ], [ 0, 0, 0, 0, 0, 0, 0, 0 ], [ 0, 0, 3, 4, 0, 5, 0, 0 ] when stored sparse as DCSC prints as ---- Sparse Tensor ---- nse = 5 pos[0] : ( 0, 4, ) crd[0] : ( 0, 2, 3, 5, ) pos[1] : ( 0, 1, 3, 4, 5, ) crd[1] : ( 0, 0, 3, 3, 3, ) values : ( 1, 2, 3, 4, 5, ) ----	2024-02-28 12:33:26 -08:00