microsoft / microsoft/DirectXShaderCompiler
[Validator] Improved diagnostics for InstrOpConstRange failures
Open
Nobody has claimed this yet.
enhancement
validation
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
InstrOpConstRange validation diagnostics are not very descriptive. For example, CreateHandle* operations will always report InstrOpConstRange with no additional context about which parameter is out of range.
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 locating the InstrOpConstRange validation and the diagnostics emitted for CreateHandle* operations. Trace how the failing parameter is identified, then update the diagnostic to include that context. Done means out-of-range parameters produce descriptive diagnostics instead of only reporting InstrOpConstRange.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100