This patch updates the remaining SparseCompiler integration tests to
target SVE when available.
TODO: Triage sparse_matmul.mlir and sparse_tanh.mlir
Differential D143514
[mlir][sparse] Port the remaining integration tests to use SVE awarzynski on Feb 7 2023, 9:49 AM. Authored by
Details This patch updates the remaining SparseCompiler integration tests to TODO: Triage sparse_matmul.mlir and sparse_tanh.mlir
Diff Detail
Event Timeline
Comment Actions
There are currently two tests that are XFAIL'ed - I will triage them shortly. Tested with:
Comment Actions Split "sparse_reduce_custom.mlir" into two tests I've split sparse_reduce_custom.mlir into:
The latter contains product reducitons that are currently supported on AArch64. We did the same for Comment Actions Note that in the long run it would perhaps be desirable to really skip the run if there is no VLA available, since we now do another similar run in most cases, which wastes testing resources. Comment Actions Thanks for reviewing! I have also thought about it and created https://github.com/llvm/llvm-project/issues/60628 to track this. Btw, I created https://github.com/llvm/llvm-project/issues/60626 for the outstanding issues with the generated output.
Comment Actions @frgossen , I'm sorry that you are hitting these issues :(
No, sorry. But perhaps we should be using fpcmp for verifying FP output 🤔 . clang-aarch64-sve-vla (which runs these tests) is green, so ideally I would avoid reverting this change. Perhaps you could blacklist the failing tests and create a GitHub ticket like https://github.com/llvm/llvm-project/issues/60626? We may need to approach this on a case-by-case basis. Comment Actions Fix in https://reviews.llvm.org/D143674 (our new push_back uses size/capacity a bit different, so a vector_transfer+print may see unitialized memory, which is why the enable-buffer-initialization was introduced to make sure memory is consistent) if there are issues beyond this problem, please let me know! |