Here are the current compilers with their input and output languages. Here’s an example of compiling HLSL using DXC, outputting SPIR-V, piping that into SPIRV-Cross, and outputting Metal: Click this, and you’ll be able to chain together up to 5 compilers. When a compiler outputs a language (or binary format) that can be fed into another compiler, you get an “Add Compiler” button.

Mali offline compiler - mali-sc.exe, ARM’s offline compiler tool.SPIRV-Cross - spirv-cross.exe, Khronos’s tool for disassembling SPIR-V back into high level languages (GLSL, HLSL, Metal, C++).glslang - glslangValidator.exe, Khronos’s reference GLSL compiler that also now has an HLSL frontend.DXC - dxc.exe, Microsoft’s new open-source HLSL compiler.FXC - fxc.exe, Microsoft’s legacy HLSL compiler.The exact ones shown in the dropdown will depend on the input language you have selected. You can now access the following compilers. The old Try HLSL site only supported Microsoft’s old and new HLSL compilers, so with Shader Playground I wanted to expand that. Now I’ll go into more detail on some of these. s: share links to a specific “playground”, with input code and all the compilation steps saved.Compiler chaining: create multiple compilation steps, so you can pipe HLSL to SPIR-V to Metal, for example.

Multiple input languages (HLSL and GLSL, with the potential for more in the future).

Given the diversity of today’s shader landscape (GLSL, SPIR-V, Metal, etc.), I wanted to make it better. It only worked with HLSL, and it only worked with Microsoft’s two HLSL compilers. However, the Try HLSL website was always a bit limited. It’s been quite popular - I don’t have stats on it, but my recent tweet about it was RT’d quite a bit, so I think this is something that people find useful. It was really very simple - type or paste HLSL code on the left, choose whether to compile with the old ( fxc.exe) or new ( dxc.exe) HLSL compilers, and see the disassembly (or compiler errors) on the right. That was why I made the Try HLSL website, first for myself and then I put it online last year. I frequently want to test little bits of shader syntax to see what the compiler does. You can share s to shaders.Īs you may know, I am very interested in shaders and shading languages ( exhibit A, exhibit B, exhibit C, exhibit D, exhibit E). You can chain multiple shader compilers together to transpile one language to another. You can see the compiler output and disassembly. You can compile HLSL and GLSL using fxc.exe, dxc.exe, glslangValidator.exe, spirv-cross.exe, and mali-sc.exe. TL/DR: I’ve made a new website called Shader Playground that is sort of like Compiler Explorer but for shading languages.

Hlsl shader viewer for mac