Orochi VS SPIRV-Cross

While you're waiting for the HIP SDK to release, check out Orochi as an alternative https://github.com/GPUOpen-LibrariesAndSDKs/Orochi

This isn't a full-fledged SDK but if you develop using the driver/runtime API and nvrtc on Linux, you could certainly use this library to make it run on Windows https://github.com/GPUOpen-LibrariesAndSDKs/Orochi Bonus - it also lets you compile a single binary that runs on both CUDA and HIP!

You can't run CUDA binaries directly. But you can use a wrapper library like Orochi to run both CUDA and HIP using a single binary that dynamically links with CUDA/HIP libraries at runtime https://github.com/GPUOpen-LibrariesAndSDKs/Orochi

I stumbled across orochi from AMD while looking for their FSR2.0 implementation, which basically boils down to being a wrapper over Cuda and HIP. I don't know if it is still maintained or functional, but heres the link if anyone is interested: https://github.com/GPUOpen-LibrariesAndSDKs/Orochi

There also exists something like SPIRV-Cross which promises to be able to generate code from the SPIRV intermediate representation into Metal and all versions of GLSL and HLSL. I am not sure really how good it is at this point, but going forward we might start to see more high-level shader languages, that compile to SPRIV and then from there to the myriad of different shader formats different platforms expect.

If you have shaders, I believe you can use SPIRV-Cross to generate GLSL, which you can probably get to pass as OpenCL C with just a bunch of macro tweaks, or at worst some small changes to spv-cross.

Regarding reflection, here is a guide: https://github.com/KhronosGroup/SPIRV-Cross/wiki/Reflection-API-user-guide

I am working on an engine that targets Vulkan and Metal. I'm at the point now where I want to be able to dynamically update my shader at runtime to suit the type of data being sent in for drawing. I am currently using offline compilation for my GLSL (for Vulkan) and MSL (for Metal) shaders. What are your workflows for situations like this? For those using tools like SPIR-V Cross and shaderc, what has your experience been with these tools keeping up to date with the latest features in the specs?

For cross-platform support look at WebGPU and Vulkan (e.g,: [0] [1]. Essentially, you would need to write the func in WGSL or GLSL, HLSL or MSL. Each of these can be cross-compiled to SPIR-V (what Vulkan needs) with cross-compilers such as spirv-cross and naga.

Just for reference, the library I'm using (both for compiling the shaders and for reflection), is SPIRV-Cross by the Khronos Group and here you have the docs for the reflection API. I wanted to check out `glslang` but honestly this one so far has worked like a charm.

Aside from SPIRV-Reflect, if you're using SPIRV-cross to cross compile your shaders, there is also a --reflect arg you can pass which spits out reflection info in JSON format. We already need to cross compile from spirv, so it just removes a tool in the chain to depend on.

For your own engine, use the format your API uses. If you need crossplatformness, there is a new path available. Write your shaders in a language that compiles to SPIR-V (HLSL/GLSL are the most obvious languages), and then use SPIR-V Cross to compile the SPIR-V back to HLSL/GLSL for other API to consume.