[mlir][spirv] Add integration tests for `vector.shuffle` / `vector.interleave`

[kuhar]

These go through several layers of decomposition / unrolling / emulation when targeting SPIR-V and it would be good to have e2e coverage there.

The new tests should be added under: https://github.com/llvm/llvm-project/tree/main/mlir/test/mlir-vulkan-runner

[llvmbot]

@llvm/issue-subscribers-mlir-spirv

Author: Jakub Kuderski (kuhar)

These go through several layers of decomposition / unrolling / emulation when targeting SPIR-V and it would be good to have e2e coverage there.

The new tests should be added under: https://github.com/llvm/llvm-project/tree/main/mlir/test/mlir-vulkan-runner

[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. Check that no other contributor has already been assigned to this issue. If you believe that no one is actually working on it despite an assignment, ping the person. After one week without a response, the assignee may be changed.
2. In the comments of this issue, request for it to be assigned to you, or just create a pull request after following the steps below. Mention this issue in the description of the pull request.
3. Fix the issue locally.
4. Run the test suite locally. 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.
5. Create a Git commit.
6. Run git clang-format HEAD~1 to format your changes.
7. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation. Mention this issue in the description of the pull request.

If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.

[llvmbot]

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

Author: Jakub Kuderski (kuhar)

These go through several layers of decomposition / unrolling / emulation when targeting SPIR-V and it would be good to have e2e coverage there.

The new tests should be added under: https://github.com/llvm/llvm-project/tree/main/mlir/test/mlir-vulkan-runner

[Rajveer100]

@kuhar
Could you give a comprehensive insight about what has to be done?

[joker-eph]

Can we avoid using the Vulcan runner and start writing tests using the mlir-cpu-runner by now? Is there anything missing?

[rengolin]

Can we avoid using the Vulcan runner and start writing tests using the mlir-cpu-runner by now? Is there anything missing?

Agreed. We should probably create a plan to deprecate the vulkan runner and rename the mlir-cpu-runner into just mlir-runner.

[kuhar]

@antiagainst for vulkan runner impl

[kuhar]

Ah, we have a tracking issue for vulkarn runner already: #73457

[antiagainst]

Yes. An there are interested contributors there. I asked them about the updates. To me the test is disjoint to the harness though. I think we should be able to add more tests while upgrading the harness.