KhronosGroup / KhronosGroup/SPIRV-Tools
[OpenCL validation] OpTypeInt
Open
component:validation
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 709
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 28
Description
From the environment spec:
```
For all OpTypeInt integer type-declaration instructions:
- Signedness must be 0, indicating no signedness semantics.
```
Contributor guide
Research direction
Start by locating the OpTypeInt validation entry point and its existing validation tests; the issue does not name files. Check how integer type-declaration operands are validated against the environment spec. Done means validation rejects nonzero Signedness for every OpTypeInt and regression coverage demonstrates the rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100