KhronosGroup / KhronosGroup/OpenCL-CTS
Integrate the SPIR-V validator
Open
cognizant-backlog
missing-coverage
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
There are a number of places where we should make use of the SPIR-V validator:
* to check the output of the offline compilation flow
* to check that the checked-in SPIR-V binaries are correct as part of the continuous integration.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the offline compilation flow, the checked-in SPIR-V binaries, and the continuous-integration configuration mentioned in the issue. Determine how the SPIR-V validator can be invoked in each path; done means offline outputs and checked-in binaries are validated, with CI rejecting invalid binaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100