DirectXShaderCompiler

Ah yes, you are right, WebGL shaders are translated first to GLSL or HLSL with a lib like ANGLE (https://github.com/google/angle). And that source is then send on to the drivers which compile it again to assembler for the graphic card. And there again are some differences between GLSL/HLSL it seems. If I remember right in GLSL the drivers do the work while in HLSL some DLL from MS produces another intermediate format (which I just found out seems to be even open source: https://github.com/Microsoft/DirectXShaderCompiler).

"For one, all shaders would need to be converted from HLSL to GLSL, which could become quite a big task depending on the amount of shaders, and testing of all changes." Ironically Microsoft have open-sourced a Clang-based HLSL compiler that could be used as a front-end for a Vulkan backend. https://github.com/Microsoft/DirectXShaderCompiler https://blogs.msdn.microsoft.com/directx/2017/01/23/new-dire...

And it's fixed! =] https://github.com/Microsoft/DirectXShaderCompiler/pull/33 https://github.com/Microsoft/DirectXShaderCompiler/issues/30

While it's really nice they built this on open source compiler infrastructure, it's also too bad they took all the LLVM code and changed the license headers on it (additionally pretending to relicense it and changing the copyright string) when that's 100% not okay: https://github.com/Microsoft/DirectXShaderCompiler/blob/mast... I'm sure it was a script, but this needs to be fixed, stat. Sadly, not even the first time: https://github.com/Microsoft/WinObjC/issues/35 https://news.ycombinator.com/item?id=10024377 https://news.ycombinator.com/item?id=10018208 (which devolved into a licensing discussion) It'd be nice if folks paid a little more attention, because for releases from large companies, stuff spreads quickly, which means a year from now, there are still likely to be "mit licensed" copies of this that are still wrong :(