What would the difficulty be to go in the opposite direction? about dxil-spirv HOT 12 CLOSED

@iwubcode We extracted the relevant bits from the MESA repository and now go via NIR. Probably still not ideal,but it works a lot better than SPIRV Cross -> HLSL -> DXIL.

Still hoping this project or another would write a dedicated converter at some point, as I think it should probably be easier to go SPIRV->DXIL, given how complex DXIL is in comparison.

godotengine/godot#70315

from dxil-spirv.

Have you considered doing SPIR-V -> HLSL with SPIRV-Cross and then running that through dxc?

from dxil-spirv.

Yes, but for performance (and amount of failure points) reasons a more direct approach may be preferred.

from dxil-spirv.

DXIL to SPIR-V

This is exactly what this project does.

from dxil-spirv.

@doitsujin my mistake, meant the opposite way.

from dxil-spirv.

https://gitlab.freedesktop.org/mesa/mesa/-/tree/main/src/microsoft/spirv_to_dxil

from dxil-spirv.

@nanokatze I think I have seen this in the past, but it relies for the most part on the Mesa IL right? Its a huge amount of code. Maybe it could be extracted?

from dxil-spirv.

Emitting LLVM (has to be 3.7 version specifically) is a bit of a shitshow, but that's the main issue with emitting DXIL, although it is completely out of scope of this project. RenderDoc should have a DXIL emitter I think, although not sure how practical that is to use for SPIR-V translation.

Another issue is emitting the DXIL in the exact way that DXIL validators like. It's not documented at all, but not exactly sure how difficult it is to deal with.

Emitting subgroup operations properly is also quite awkward with control flow (or lack there of) being what it is in DXIL.

from dxil-spirv.

@HansKristian-Work

I see, its kind of a shame that no simple way to do this conversion exists. SPIRV-Cross has it out of scope, as well as this project. MESA has a converter but its entirely dependent on lots of MESA files.

This makes it very difficult to work on multi platform code that uses SPIR-V universally, as it is not possible to easily/efficiently convert to DXIL.

from dxil-spirv.

Do you also support DX11? You'll probably have the same problem with DXBC there.

from dxil-spirv.

No, no interest from our part in suporting DX11, only Vulkan level APIs.

from dxil-spirv.

@reduz - curious what you ended up doing? Currently we use glsang to take GLSL to SPIRV and then SPIRV-Cross to go to HLSL...then go to DXIL (DX12 backend) and DXBC (DX11 backend). It works but it's in realtime and is quite slow, cutting out a step would be very helpful (even if only for DX12).

I did open an issue on DirectXShaderCompiler but not expecting much.

from dxil-spirv.