Re:Adding HLSL and DirectX Support to Clang and LLVM
by ruph123 on Saturday March 12, 2022 @02:42AM
(#30649731)
Can someone please explain why this is is problematic?
[ Parent
| on HN ]
Re:Adding HLSL and DirectX Support to Clang and LLVM
by pjmlp on Saturday March 12, 2022 @03:30AM
(#30649935)
On most 3D APIs, with exception of OpenGL (and its Web variants), shaders are shipped as binaries, so if the driver expects another version that game won't play.
Re:Adding HLSL and DirectX Support to Clang and LLVM
by hyperman1 on Saturday March 12, 2022 @03:25AM
(#30649916)
I assume they can't upgrade to more recent LLVM versions, as the 3.7 bitcode is now found in a ton of published games. If they move to, say, 3.8, they need a LLVM 3.7 to 3.8 bitcode translator.
Basically, microsoft published someone else's unstable, unsupported API.
Re:Adding HLSL and DirectX Support to Clang and LLVM
by my123 on Saturday March 12, 2022 @04:38AM
(#30650239)
> they need a LLVM 3.7 to 3.8 bitcode translator.
LLVM IR provides upwards compatibility, that’s not what the issue is.
The issue is rather having your game binaries not work at all on older OS/driver releases when built with a newer LLVM version.