KhronosGroup / KhronosGroup/SPIRV-Tools
spirv-fuzz: consistently log cases where we give up
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 709
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 28
Description
We should output a log message with a consistent format when we give up due to assumptions being violated (because we just wanted to handle the most common, simple cases). We should get gfauto to collect these messages so we remain aware of when we hit these in practice, and thus where we could improve spirv-fuzz by handling more complex scenarios.
Contributor guide
Research direction
Start by locating the spirv-fuzz paths that give up after assumptions are violated, then inspect how gfauto collects runtime messages. Define a consistent log format for these cases and verify that gfauto captures them so the occurrences remain visible in practice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100