KhronosGroup / KhronosGroup/Vulkan-Docs
Missing VUIDs for `offset + extent` being in bounds of the image subresource in `VkSparseImageMemoryBind`
Open
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
[`VkSparseImageMemoryBind`](https://registry.khronos.org/vulkan/specs/latest/man/html/VkSparseImageMemoryBind.html) doesn't have any VUIDs for ensuring that `offset + extent` is in bounds of the image subresource, which looks like an oversight.
Contributor guide
Research direction
Start with the VkSparseImageMemoryBind reference in the Vulkan specification and compare its existing validity requirements with the image-subresource bounds rules. Define the missing VUID coverage for offset plus extent being in bounds, then verify the specification's generated reference output reflects the new requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100