KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
missing VUs for externally synchronized
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
We track things in the spec with "must be externally synchronized" already in thread safety, these seem to just be a few cases where we had to have an explicit VU for it
- [ ] VUID-vkMergePipelineCaches-dstCache-10202
- [ ] VUID-vkUpdateDescriptorSetWithTemplate-descriptorSet-06995
- [ ] VUID-vkUpdateDescriptorSets-pDescriptorWrites-06993
- [ ] VUID-vkCreateComputePipelines-pipelineCache-02873
- [ ] VUID-vkCreateGraphicsPipelines-pipelineCache-02876
- [ ] VUID-vkCreateRayTracingPipelinesKHR-pipelineCache-02903
- [ ] VUID-vkCreateRayTracingPipelinesNV-pipelineCache-02903
- [ ] VUID-vkCreateDataGraphPipelinesARM-pipelineCache-09762
Contributor guide
Research direction
Search the repository and Vulkan spec references for the listed VUIDs, then inspect how existing externally synchronized requirements are represented. Done means all eight listed cases have their explicit VUs represented consistently with the existing thread-safety handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100