Just a few days ago, LLVM accepted DirectX as one of its official compilation targets. After four years of work driven by Microsoft, the free Clang compiler will be able to generate DirectX shaders without external pieces and with HLSL enabled by default starting with the future version 24.
The news sounds like "magic science" for compilers, but in reality, it directly affects the world of video games. Whoever programs a game's visual effects writes their code once in a language such as HLSL, and today needs different tools depending on the destination, which complicates porting a game to different platforms. With this step, Windows, Linux and macOS come closer to sharing the same entry point.
And it is worth noting that all of this arrives at a sweet moment for gaming on Linux, with Proton and Steam Deck in full form.
Four years of experimental work come to an end
For four years, DirectX support lived inside LLVM as an experiment disabled by default. The tools had to be compiled by hand and a hidden option enabled to use it, so almost no one outside Microsoft touched it. But that is over.
The formal proposal was signed by Microsoft engineer Farzon Lotfi in early August on the LLVM forum, and the promotion patch has already been accepted. The change takes the backend out of its experimental status and enables by default the clang-dxc, which understands HLSL directly.
The key lies in what it produces. This backend translates the code to DXIL, the format consumed by Windows graphics drivers with DirectX 12. That means it is not an API translator, nor an emulator. It is the missing link for the standard open source compiler to speak the GPU language on Windows, fully natively, opening the door to migrating DX12 games to Linux in a much simpler way.
Even so, it is worth keeping our feet on the ground. Current maturity is equivalent to that of the DXC compiler in compute shaders, while graphics shaders and ray tracing remain future work, along with the newer Shader Models. The proposal itself says so bluntly and asks for more eyes on the code to polish conformance and performance. The team also boasts a conformance suite that compares what Clang and DXC generate in various environments, using LLVM's standard test infrastructure.
Valve releases Proton 11 and gains ground on Windows in gaming
What changes for those who play on Windows and on Linux
On Windows the effect is direct. Developers will be able to compile their shaders with a normal Clang, without depending on a separate fork of LLVM maintained apart. Fewer moving pieces, fewer divergences and a shorter path between the code and the driver.
On Linux the effect is indirect, but perhaps more exciting. Here there are no DirectX drivers nor will there be. What there is is formidable translation machinery. Proton, DXVK and VKD3D-Proton convert DirectX calls into Vulkan so that thousands of Windows games work on Linux and Steam Deck.
And that machinery is at its best moment. DXVK 3.0, published in June, debuted a new shader compiler that fixes bugs previously impossible to solve and requires Vulkan 1.4. VKD3D 2.1, which arrived in August, went deeper into DXIL support and DirectX 12 mesh shaders. Everything points in the same direction.
The problem is that each path spoke its own dialect of tools. An HLSL compiled and verified with LLVM's standard infrastructure is an HLSL that translation layers can trust more. In this way, the same language reliably feeds both the native Windows driver and the translators that bring it to Vulkan on Linux.
The context helps to understand the enthusiasm. Valve has spent years turning Linux into a serious gaming platform with Proton, and the Steam Deck proved that thousands of Windows titles can be experienced outside Windows. Every improvement in the shader chain shows up in loading times, stutters and games that stop failing.
There is also a silent proof of this convergence. LLVM's test suite runs the same HLSL shaders on DirectX 12, Vulkan and Metal, even from Linux thanks to the DirectX bridge in WSL 2, available since 2020. Three APIs, a single language, a single test suite.
macOS does not run DirectX either, and that is not going to change. Its strong suit is Metal, the native graphics API of macOS, and the bridge for it already exists. The DXC compiler can generate Metal libraries directly with its -metal flag, relying on Apple's official converter, as the project itself documents.
This is where LLVM's move makes full sense. If HLSL is compiled with standard and open tools, converting it to Metal stops being an exercise in craftsmanship with a private fork. Clang's documentation sets this out as a long-term goal. To achieve it, the free compiler should cover all of DXC's current uses, including Vulkan and Metal as destinations.
In February of this year, Microsoft announced the creation of the Ecma TC57 committee to turn HLSL into an open and royalty-free standard, with industry participation on equal terms. The announcement describes HLSL as a multiplatform language whose future already exceeds Microsoft's borders. Eleven years after adopting it as the basis of DXC, LLVM returns the favor by welcoming DirectX as a first-class citizen.
Flathub, the Linux App Store that has already surpassed 4 billion downloads
Writing the future with SPIR-V
But there is one more piece and it is the most ambitious. In September 2024, Microsoft announced that DirectX 12 will accept shaders compiled in SPIR-V, the open format of the Khronos group already used by Vulkan and OpenCL. Support will be official when Shader Model 7 arrives in DirectX 12. Maintaining a proprietary format, the DirectX team admitted at the time, clashes with its commitment to open technologies, and is a blessing for gamers and modders.
Two years later, the plan is still on course. The February 2026 edition of the compiler brought deep improvements in SPIR-V generation to interoperate better with Vulkan drivers, in addition to production support for Shader Model 6.9. And Microsoft promises tools to translate between SPIR-V and DXIL in both directions during the transition, which will be long. The precedent invites optimism, because SPIR-V support in DXC was contributed by a Google team and its maintenance remains in shared hands.
The map looks like this.
| System |
How it receives HLSL shaders today |
What the LLVM milestone contributes |
| Windows |
DXIL directly to the DirectX 12 driver |
Standard compiler in Clang, without a separate fork |
| Linux |
Translation to Vulkan via Proton, DXVK and VKD3D |
An HLSL verified with the same tools |
| macOS |
Conversion to Metal with Apple's converter |
Open and standard HLSL, easier to convert |
It is not a miracle…for now
No official backend installs DirectX drivers on Linux or magically revives broken games. To calibrate expectations, three nuances weigh heavily.
First, parity with DXC today covers compute shaders. Graphics and ray tracing are still on the roadmap, so AAA studios are not going to ditch their current toolchain tomorrow morning.
Second, DXIL carries a peculiar legacy. The format is anchored to the bitcode of LLVM 3.7, a version from a decade ago. During the promotion debate, the question was raised whether that would freeze the design of LLVM's debug information, and the answer reassured people. The backend degrades that information to the old intrinsics and discards what does not fit, without blocking the rest of the project.
Third, Shader Model 7 with SPIR-V still has no date. The total unification of the shader format is a multi-year project, not next spring's.
Even so, the direction is unmistakable. Every piece, the official backend, standardized HLSL and SPIR-V as the horizon, reduces the friction of publishing a game outside Windows. And of one thing we can be sure: Linux and macOS gamers will be grateful.
New console generation: PS6, Xbox and the RAM crisis