Skip to content

sycl/test should not be repeated for different triples #14671

@AlexeySachkov

Description

@AlexeySachkov

Is your feature request related to a problem? Please describe

This issue is describing a potential internal improvement we can make to our testing infrastructure making our codebase simpler and testing time lower.

We currently define a bunch of targets to launch check-sycl with different triples, like:
https://github.com/intel/llvm/blob/c5ed6e21ef941c874a6d8ee61c0e4b3b23a4aac4/sycl/test/CMakeLists.txt#L97-104

sycl/test are written in assumption and there is no guarantee that any of devices are available and that we can actually launch anything. Therefore, this suite is for checking compilation of SYCL headers and integration of headers with compiler (like checking that the right IR/SPIR-V is produced from a proper SYCL example by our toolchain).

Even if we have some tests which are specific for a backend, they should set the right triple explicitly and we don't need to repeat every other test for a different triple for that.

Describe the solution you would like

No response

Describe alternatives you have considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions