Make `naga` validation errors easier to debug
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Currently when naga fails validation (when using wgpu +rust-gpu for the web) it can be really confusing and really hard to debug:
- https://github.com/Rust-GPU/rust-gpu/discussions/23
- https://github.com/Rust-GPU/rust-gpu/discussions/203
We should make it better so it is obvious what naga-generated code is causing the failure and how it maps to the rust-gpu input
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 reviewing the validation-debugging cases in discussions 23 and 203 and the naga failures described in this issue. Define what information is needed to identify naga-generated code and map it back to rust-gpu input; done means those failures become substantially easier to trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100