KhronosGroup / KhronosGroup/SPIRV-Tools
[OpenCL validation] Scope for Memory
Open
component:validation
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 709
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 28
Description
_Scope_ for _Memory_ is generally limited to:
- **CrossDevice**
- **Device**
- **Workgroup**
- **Invocation**
On OpenCL 2.1/2.2:
- **Subgroup** is allowed as well (what to do with 2.0+cl_khr_subgroups?)
Contributor guide
Research direction
Review the OpenCL validation rules for Memory scope, especially the listed CrossDevice, Device, Workgroup, and Invocation scopes. Determine how OpenCL 2.1/2.2 and 2.0 with cl_khr_subgroups should treat Subgroup, then confirm the intended validation behavior and update the relevant validation coverage.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100