KhronosGroup / KhronosGroup/OpenCL-Docs
SPIR-V: Require a Storage Class for Barrier Memory Semantics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
The OpenCL SPIR-V Environment Spec currently does not document behavior if there is no Storage Class specified in the Memory Semantics for OpMemoryBarrier or OpControlBarrier.
Since a missing Storage Class for these instructions is mostly likely an error, I think lack of a Storage Class should be considered an error and make a SPIR-V module invalid. This behavior would be consistent with the Vulkan SPIR-V Environment.
Issue #91 is slightly related, but I think it is different enough and we should track this issue separately.
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 by locating the OpenCL SPIR-V Environment Spec section covering OpMemoryBarrier and OpControlBarrier, then compare its wording with the linked Vulkan SPIR-V Environment specification. Done means the OpenCL specification explicitly treats a missing Storage Class in these memory semantics as an error that makes the SPIR-V module invalid.
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