KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Add VK_ATTACHMENT_DESCRIPTION_MAY_ALIAS_BIT check
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
- VUID-vkCmdBeginRenderPass-framebuffer-02532
- VUID-vkCmdBeginRenderPass2-framebuffer-02533
- VUID-vkCmdBeginRenderPass-framebuffer-09045
- VUID-vkCmdBeginRenderPass2-framebuffer-09046
- VUID-VkRenderPassCreateInfo2-attachment-03050
- VUID-VkRenderingInfo-None-09044
Discussed in https://gitlab.khronos.org/vulkan/vulkan/-/issues/4622
if both `VkImage` are bound to the **same** `VkDeviceMemory` you are able to validate
The way to check this is to get the size (with `vkGetImageMemoryRequirements`) and use the `VkBindImageMemory` to know the `['memoryOffset', 'memoryOffset'+size]` range
Contributor guide
Research direction
Start by reading the listed VUIDs and the validation paths for vkCmdBeginRenderPass, vkCmdBeginRenderPass2, and VkRenderingInfo. Examine vkGetImageMemoryRequirements and VkBindImageMemory to understand the memory ranges described in the issue. Done means overlapping bindings to the same VkDeviceMemory are detected for the listed cases, with validation coverage for each VUID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100