microsoft / microsoft/DirectXShaderCompiler
`register` binding applied to `static` variable declaration should be an error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
Description
If a user declares a static variable of a resource type and assigns a register binding to it DXC ignores the register binding and compiles the code which can result in runtime failures or validation errors.
In Clang we correctly made this an error, see:
https://godbolt.org/z/9oWrxjs11
Steps to Reproduce
https://godbolt.org/z/xbTKd9rvq
Actual Behavior
This should produce a frontend error diagnostic, instead it may produce a validation error under SM 6.5, or fail at runtime under SM 6.6+.
Environment
- DXC version: 1.6+
- Host Operating System: All
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 with the Steps to Reproduce Godbolt example and compare its DXC behavior with the Clang example linked in the description. Trace the frontend handling of a static resource variable with a register binding, then add coverage where appropriate; done means DXC emits a frontend error diagnostic instead of compiling it.
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
- Mostly clear
- Newbie friendliness
- 45/100