tree 90451bab8542e18ea4ee447d88993f679e675970
parent caffd15fa261cdf0fd0260b424d15c5d5484d15a
author Nicolas Capens <capn@google.com> 1632753018 -0400
committer Nicolas Capens <nicolascapens@google.com> 1633108599 +0000

Add padding to VkBuffer size to avoid access violation

By adding 15 bytes of padding, any vertex attribute within the buffer
can be read using accesses that are up to 16 bytes wide. This helps
performance by avoiding having to break up some accesses into multiple
smaller ones, and avoids code bloat.

Note that we detect when numerical overflow happens, which would
typically only occur in tests that want to force an allocation that
can't succeed, using a buffer of size 0xFFFFFFFFFFFFFFFF. We don't
test against vk::MAX_MEMORY_ALLOCATION_SIZE or PHYSICAL_DEVICE_HEAP_SIZE
because that would silently avoid valid usage violations such as
VUID-vkAllocateMemory-pAllocateInfo-01713.

This change also temporarily increases the memory heap size by 15 bytes,
to work around an ANGLE bug.

Bug: b/201282910
Bug: angleproject:6444
Change-Id: I9489c0a1e51e9986f49a4b25d3aca3858778f47a
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/57568
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>