KhronosGroup / KhronosGroup/Vulkan-Portability
Add VkPhysicalDevicePortabilitySubsetFeaturesKHR:: shaderTessellationInputOutputBarrier capability
- Dominant language
- No language data
- Stars
- 45
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some CTS tests fail when using barriers between tessellation stages.
This might be 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:: shaderTessellationInputOutputBarrier` capability.
This affects 1 CTS tests:
```
dEQP-VK.tessellation.shader_input_output.barrier
Fail (Failure)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Vulkan Portability subset feature definitions and reviewing the named CTS test, dEQP-VK.tessellation.shader_input_output.barrier. Add the requested shaderTessellationInputOutputBarrier capability so this use case can be reported as Not Supported, then verify the affected CTS result.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100