The boilerplate was setting up some arrays for testing. To fully illustrate
python - MLIR potential, however, this data should also come from numpy land.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
| mlir/test/python/dialects/sparse_tensor/test_SpMM.py | ||
|---|---|---|
| 57–61 | Can we document that the first argument of main is first converted to sparse tensor with the given attr before calling the generated kernel? | |
| 104–109 | go/pystyle#naming | |
| 106 | Now that we can see the input tensors here, can we use numpy to compute the expected result instead? | |
| 111–117 | Similar to the above, maybe we want to use c_a_memref_ptr etc? | |
| mlir/test/python/dialects/sparse_tensor/test_SpMM.py | ||
|---|---|---|
| 106 | Ah yes, good idea! | |
Can we document that the first argument of main is first converted to sparse tensor with the given attr before calling the generated kernel?