SPIRV-Cross VS anydsl

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.

I work on the AnyDSL research project, we have our own IR and optimizing compiler (Thorin), our framework supports partial evaluation and efficient codegen for the host as well as multiple compute offload targets (CUDA, OpenCL C, the NVVM and AMDGPU targets in LLVM), and I've been pursuing targeting SPIR-V as well.

There is also this:

https://anydsl.github.io/

They have some framework that achieves high level compute!

While waiting for std::simd to become a thing in stable and looking for alternatives I stumbled upon this: https://anydsl.github.io/

I had a look at Impala previously. It describes itself as dialect of Rust, but somehow I'm not exactly happy with Rust syntax, but found Impala's much more cuter, up to actually bother to report a doc glitch to make it even more cuter to passers-by ;-). I understand that it's pretty hard to bootstrap a language nowadays, so understand that "any DSL" marketing niche, though I guess it wouldn't look bad if it was promoted as a general-purpose language either. I also understand that it's open-source, but I'm not rushing to look there, by various reasons, like complexity, copyright and possibility to pick up bad ideas ;-). Preferring to do "black box" studying by papers for now, so thanks again for the links.