Folding in the MLIR uses the order of the type directly
but folding in the underlying implementation must take
the dim ordering into account. These tests clarify that
behavior and verify it is done right.
Details
Details
- Reviewers
- bixia 
- Commits
- rG758ccf8506c3: [mlir][sparse] add test for DimOp folding
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
| Time | Test | |
|---|---|---|
| 80 ms | x64 windows > Flang.Driver::output-paths.f90 | 
Event Timeline
| mlir/test/Dialect/SparseTensor/conversion.mlir | ||
|---|---|---|
| 66 | can we make the irrelevant dims unknown, such as ?x20x?xf64? | |
| mlir/test/Dialect/SparseTensor/conversion.mlir | ||
|---|---|---|
| 66 | I could, but why do you think that is better? If you want, I can add another test with that. | |
| mlir/test/Dialect/SparseTensor/conversion.mlir | ||
|---|---|---|
| 66 | 10x20x30 is a static shape but ?x20x? is a dynamic shape. | |
can we make the irrelevant dims unknown, such as ?x20x?xf64?