KhronosGroup / KhronosGroup/Vulkan-Portability
Add VkPhysicalDevicePortabilitySubsetFeaturesKHR:: shaderSharedVariableReleaseAcquire capability
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 45
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some CTS tests fail on shader releasing and acquiring shared variables.
This is most likely fixable with effort within the implementations.
In the meantime, these use cases can be disabled in CTS and reported as Not Supported, by adding a VkPhysicalDevicePortabilitySubsetFeaturesKHR:: shaderSharedVariableReleaseAcquire capability.
This affects 2 CTS tests:
dEQP-VK.memory_model.message_passing.permuted_index.release_acquire
dEQP-VK.memory_model.message_passing.permuted_index.release_acquire_atomic_payload
Fail (Fail)
Contributor guide
No contributing guide indexed for this repository
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 portability-subset feature definitions and the CTS handling for dEQP-VK.memory_model.message_passing.permuted_index.release_acquire and release_acquire_atomic_payload. Confirm how unsupported capabilities are reported, then add the shaderSharedVariableReleaseAcquire capability so both tests report Not Supported; run these CTS tests to verify the result.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100