Bug 1885217 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Microsoft's DXC is a successor to FXC that fixes these issues. We could consume it, and thereby resolve the above problems. Another approach might be to write a compilation backend for Firefox's shader transpiler (Naga) for DXIL, so we can emit it directly.

:jgilbert has noted that our most likely path to success is to work with Microsoft directly, and ensure that DXC is suitable to ship for us if we run into obstacles.
Microsoft's DXC is a successor to FXC that fixes these issues. We could consume it, and thereby resolve the above problems. Another approach might be to write a compilation backend for Firefox's shader transpiler (Naga) for DXIL, so we can emit it directly (viz., [`wgpu`#4155](https://github.com/gfx-rs/wgpu/issues/4155)).

:jgilbert has noted that our most likely path to success is to work with Microsoft directly, and ensure that DXC is suitable to ship for us if we run into obstacles.
Microsoft's [DirectX Shader Compiler](https://github.com/microsoft/DirectXShaderCompiler) (AKA "DXC") is a successor to FXC that fixes these issues. We could consume it, and thereby resolve the above problems. Another approach might be to write a compilation backend for Firefox's shader transpiler (Naga) for DXIL, so we can emit it directly (viz., [`wgpu`#4155](https://github.com/gfx-rs/wgpu/issues/4155)).

:jgilbert has noted that our most likely path to success is to work with Microsoft directly, and ensure that DXC is suitable to ship for us if we run into obstacles.
Microsoft's [DirectX Shader Compiler](https://github.com/microsoft/DirectXShaderCompiler) (AKA "DXC") is a successor to FXC that fixes these issues. We could consume it, and thereby resolve the above problems. Another approach might be to write a compilation backend for Firefox's shader transpiler (Naga) for [DXIL](https://github.com/microsoft/DirectXShaderCompiler/blob/5852de760be2e0e70ee62fa427e0ff5a86dafc23/docs/DXIL.rst) (DXC's new intermediate representation), so we can emit it directly (viz., [`wgpu`#4155](https://github.com/gfx-rs/wgpu/issues/4155)).

:jgilbert has noted that our most likely path to success is to work with Microsoft directly, and ensure that DXC is suitable to ship for us if we run into obstacles.
Possible solutions we know of so far:

* Microsoft's [DirectX Shader Compiler](https://github.com/microsoft/DirectXShaderCompiler) (AKA "DXC") is a successor to FXC that fixes these issues. We could consume it, and thereby resolve the above problems.
* Another approach might be to write a compilation backend for Firefox's shader transpiler (Naga) for [DXIL](https://github.com/microsoft/DirectXShaderCompiler/blob/5852de760be2e0e70ee62fa427e0ff5a86dafc23/docs/DXIL.rst) (DXC's new intermediate representation), so we can emit it directly (viz., [`wgpu`#4155](https://github.com/gfx-rs/wgpu/issues/4155)).

:jgilbert has noted that our most likely path to success is to work with Microsoft directly, and ensure that DXC is suitable to ship for us if we run into obstacles.

Back to Bug 1885217 Comment 1