Implement SYCL code cache

[sommerlukas]

Implement a SYCLCodeCache similar to the CUDACodeCache for compilation of CUTLASS code for integration of the CUTLASS SYCL backend into Pytorch TorchInductor.

Also changes the third-party submodule for CUTLASS to use Codeplay's fork with the SYCL backend.

[sommerlukas]

The current PR only moves the cutlass_dir configuration variable from the cuda sub-config into the common config.

Here, there is a number of additional CUTLASS-related options. If they're interesting for our CUTLASS code generation, we could either duplicate them or also move them to the common config.

[OuadiElfarouki]

The current PR only moves the cutlass_dir configuration variable from the cuda sub-config into the common config.

Here, there is a number of additional CUTLASS-related options. If they're interesting for our CUTLASS code generation, we could either duplicate them or also move them to the common config.

Yes thanks @sommerlukas, indeed a lot can be factorized outside a sycl or cuda scope and I'm seeing this at multiple levels, this would be co-designed alongside the rest of the codegen & template/kernel classes, namely the CUTLASSArgs class for instance. All seems good otherwise thanks.

[sommerlukas]

The current PR only moves the cutlass_dir configuration variable from the cuda sub-config into the common config.
Here, there is a number of additional CUTLASS-related options. If they're interesting for our CUTLASS code generation, we could either duplicate them or also move them to the common config.

Yes thanks @sommerlukas, indeed a lot can be factorized outside a sycl or cuda scope and I'm seeing this at multiple levels, this would be co-designed alongside the rest of the codegen & template/kernel classes, namely the CUTLASSArgs class for instance. All seems good otherwise thanks.

Do you want this to be done or later on? My thinking so far was that we would extract the options once we use them for SYCL code generation in future PRs.

[OuadiElfarouki]

The current PR only moves the cutlass_dir configuration variable from the cuda sub-config into the common config.
Here, there is a number of additional CUTLASS-related options. If they're interesting for our CUTLASS code generation, we could either duplicate them or also move them to the common config.

Yes thanks @sommerlukas, indeed a lot can be factorized outside a sycl or cuda scope and I'm seeing this at multiple levels, this would be co-designed alongside the rest of the codegen & template/kernel classes, namely the CUTLASSArgs class for instance. All seems good otherwise thanks.

Do you want this to be done or later on? My thinking so far was that we would extract the options once we use them for SYCL code generation in future PRs.

Agree I guess it's better if we keep it for the next PRs so it makes more sense with the upcoming changes.

[OuadiElfarouki]

LGTM, Thanks Lukas for the 1st PR!

[sommerlukas]

Rebased this branch, example still working correctly. Merging now.