KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Fix VUID-vkCmdPipelineBarrier2-srcQueueFamilyIndex-01182 for Dynamic Rendering Local Read
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
`VUID-vkCmdPipelineBarrier2-srcQueueFamilyIndex-01182` (and `VUID-vkCmdPipelineBarrier-srcQueueFamilyIndex-01182`) recently was reworded to say "any memory barrier" instead of "any image memory barrier"
This was done in preparation for `VK_KHR_dynamic_rendering_local_read` (Because before you only could do it with image barriers)
Need to see if there is a way with `VK_KHR_dynamic_rendering_local_read` to have the `pMemoryBarriers` or `pBufferMemoryBarriers` also violate `VUID-vkCmdPipelineBarrier2-srcQueueFamilyIndex-01182`
Contributor guide
Research direction
Start by comparing the Vulkan requirements for VK_KHR_dynamic_rendering_local_read with VUID-vkCmdPipelineBarrier2-srcQueueFamilyIndex-01182 and VUID-vkCmdPipelineBarrier-srcQueueFamilyIndex-01182. Check whether pMemoryBarriers or pBufferMemoryBarriers can trigger the rule, and document the required validation change and coverage needed if they can.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100