microsoft / microsoft/DirectXShaderCompiler
[SPIR-V] "generated SPIR-V is invalid: Number of image operand ids doesn't correspond to the bit mask"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
Description
I seem to have run into an issue with DXC that I do not understand.
Environment
- DXC version
dxcompiler.dll: 1.6 - 1.6.2112.16 (e8295973c); dxil.dll: 1.6(101.6.2112.13) - Host Operating System Microsoft Windows Version 24H2 (OS Build 26100.3194)
- Host Machine: Microsoft Surface Pro 11 with Qualcomm Snapdragon X Plus SoC
Steps to Reproduce
Attempt to build hedge-dev/UnleashedRecomp with submodule at tools/XenonRecomp pointing to IsaacMarovitz/XenonRecomp:simde (for hedge-dev/XenonRecomp#22 in case repo gets nuked after merge)
Actual Behavior
It gets very angry.
PowerShell Transcript of manually running relevant build step
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the relevant build step from the UnleashedRecomp setup, using tools/XenonRecomp at the referenced simde revision and the linked PowerShell transcript. Inspect the generated SPIR-V and compiler validation failure to identify the responsible compiler path; done means the build no longer emits SPIR-V with mismatched image operand ids.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100