Enhance our tests for sparse kernels (medium level, independent, starter)

[aartbik]

Bugzilla Link	52307
Version	unspecified
OS	Linux
CC	@joker-eph

Extended Description

The sparse compiler relies on FileCheck based tests (https://github.com/llvm/llvm-project/tree/main/mlir/test/Dialect/SparseTensor) and "regression" test (https://github.com/llvm/llvm-project/tree/main/mlir/test/Integration/Dialect/SparseTensor/CPU). These tests make sure that the generated IR is as expected and that the lowering runs "end to end". Most of these tests were developed in conjunction with particular features while they were being added.

But we can always use more tests. Real-life kernels with higher dimensional tensors, tests with difficult co-iterating constructs, etc.

The entry requests researching new tests and adding them to our testing directories. This is a relatively independent starter project, since it can be done without a very deep knowledge of the sparse compiler internals (although insights in those always help, of course).

[aartbik]

assigned to @aartbik

[llvmbot]

Hi!

This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

1. Assign the issue to you.
2. Fix the issue locally.
3. Run the test suite locally.
   3.1) Remember that the subdirectories under test/ create fine-grained testing targets, so you can
   e.g. use make check-clang-ast to only run Clang's AST tests.
4. Create a git commit
5. Run git clang-format HEAD~1 to format your changes.
6. Submit the patch to Phabricator.
   6.1) Detailed instructions can be found here

For more instructions on how to submit a patch to LLVM, see our documentation.

If you have any further questions about this issue, don't hesitate to ask via a comment on this Github issue.

@llvm/issue-subscribers-good-first-issue

[pranav-kumar-hex]

Hello @aartbik ! I'm interested in taking this on as my first issue to work on. Can u please assign the issue to me ?

[el-ev]

@pranav-kumar-hex Assigned.

[aartbik]

@pranav-kumar-hex Thanks for your interest in this task. Do you have some ideas on what new tests to write and add?