KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Missing implementation for sync with sparse resources
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
Follow up on #9399
Some of the CTS tests that would hit this assert are:
`dEQP-VK.api.buffer.suballocation.transfer_src.transfer_dst.uniform_texel.storage_texel.uniform.storage.index.vertex.indirect.create.binding`
`dEQP-VK.memory.requirements.core.buffer.sparse`
`dEQP-VK.dgc.ext.graphics.misc.sparse_vbo_token`
`dEQP-VK.binding_model.descriptor_buffer.traditional_buffer.capture_replay.sparse_buffer_descriptor_data_consistency`
Contributor guide
Research direction
Start by reading issue #9399, then reproduce the listed CTS cases involving sparse resources. Trace the missing synchronization implementation from the failing assertions and determine the validation-layer entry points involved. Done means the affected CTS tests no longer hit the missing implementation assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100