We will support symmetric MTX without expanding the data in the sparse tensor
storage.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td | ||
---|---|---|
42–46 | please add doc that reading in a symmetric matrix will result in lower/upper triangular and that proper symmetry support is TBD | |
mlir/include/mlir/ExecutionEngine/SparseTensor/File.h | ||
169 | I think it is okay to record the symmetric property, we just don't use it to do anything special (but in the future we still want to know this information) | |
303 | keep this | |
mlir/include/mlir/ExecutionEngine/SparseTensorRuntime.h | ||
251 ↗ | (On Diff #497480) | keep this |
mlir/lib/ExecutionEngine/SparseTensorRuntime.cpp | ||
880 ↗ | (On Diff #497480) | keep |
mlir/test/Integration/data/test_complex.mtx | ||
1 ↗ | (On Diff #497480) | we can still keep the symmetric flag, just to make sure we can read it |
Address review comment: keep symmetric property, keep two tests with symmetric input with TODO, add to doc about symmetric handling is TBD.
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td | ||
---|---|---|
42–46 | did you | |
43–45 | How about: Reading in a symmetric matrix will result in just the lower/upper triangular part of | |
52–53 | does this fit on one line now? |
How about:
Reading in a symmetric matrix will result in just the lower/upper triangular part of
the matrix (so that only relevant information is stored). Proper symmetry support
for operating on symmetric matrices is still TBD.