Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[mlir][sparse] use consistent type for COO object and sparse tensor s…
…torage There was a slightly mismatch between the double COO and actual numerical type in the final sparse tensor storage (due to external formats always using double). This minor revision removes that inconsistency by using a properly typed COO and casting during the "add" method instead. This also prepares alternative ways of initializing the COO object. Reviewed By: gussmith23 Differential Revision: https://reviews.llvm.org/D107310
- Loading branch information
Showing
1 changed file
with
25 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters