KhronosGroup / KhronosGroup/Vulkan-Docs
Sparse image `offset` and `extent` are not constrained to the dimensions of the image
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
`VkSparseImageMemoryBind` has fields `offset` and `extent` to specify which part of the image the memory is bound for. There is no VUID on `VkSparseImageMemoryBindInfo` that says these values must fall within the size of the image. VUID-VkSparseImageMemoryBindInfo-subresource-01722 and VUID-VkSparseImageMemoryBindInfo-subresource-01723 apply for the mip level and array layer, but there is no constraint relating to the extent of the image (more specifically, the specified subresource of the image).
Note that the related VUID-VkSparseMemoryBind-resourceOffset-01099 and VUID-VkSparseMemoryBind-size-01100 apply this constraint for buffers and opaque image memory, so it's probably needed for images too.
Contributor guide
Assessment
This issue has not been assessed yet.