Fix robust buffer access result checking for partially out of bound cases
authorJunda Liu <Junda.Liu@amd.com>
Tue, 9 Mar 2021 08:21:32 +0000 (16:21 +0800)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 18 Mar 2021 15:11:52 +0000 (15:11 +0000)
commita755c3c848dbec11cdfc3f68d40698c042fe05c0
tree888a06850c2bd52268611df3c84a8910b6ff41dc
parent941682268f7ede28c99c72afd71fd81059bab26b
Fix robust buffer access result checking for partially out of bound cases

The spec says:
Out-of-bounds buffer loads will return any of the following values:
...
Values from anywhere within the memory range(s) bound to the buffer (possibly including bytes of memory past the end of the buffer, up to the end of the bound range).
...

So partially out of bound load may return memory content for the in bound part. E.g., loading a 64-bit value from a buffer with 3B size (allocated 4B size), the first 4B can be value within the buffer.

Affected tests:
dEQP-VK.robustness.buffer_access.through_pointers.*

Change-Id: I1fab8d3819cf4d5935904a1c7762c3660c67379b
external/vulkancts/modules/vulkan/robustness/vktRobustBufferAccessWithVariablePointersTests.cpp