KhronosGroup / KhronosGroup/OpenCL-Docs
Document SPIR-V work-group barrier requirements (OpControlBarrier)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
See discussion: https://github.com/KhronosGroup/OpenCL-Docs/pull/1375#issuecomment-2892417816
We need to add a requirement in the SPIR-V environment spec to effectively say that an OpControlBarrier with work-group scope only has defined behavior when the barrier is encountered by all work-items in the work-group and within uniform control flow. This used to be documented in the SPIR-V specification, but it was removed in SPIR-V 1.6 revision 3 because it was too strict for some types of sub-group barriers in Vulkan.
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 with the linked discussion in OpenCL-Docs PR 1375 and locate the SPIR-V environment specification sources. Confirm how OpControlBarrier with work-group scope is currently described and add the requirement for all work-items and uniform control flow. Done means the specification clearly states the defined-behavior conditions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100