Thanks. Seems like my google foo was weak.
On Fri, 8 Nov 2019 at 22:57, Chris Forbes wrote:
> This is enforcing a hard requirement in the spec:
>
> 30.1. Feature Requirements
>
> All Vulkan graphics implementations must support the following features:
>
> * robustBufferAccess
>
>
> On Fri, Nov 8
In the case of glibc, pthread_t is internally a pointer. If
lp_rast_destroy() passes a 0-value pthread_t to pthread_join(), the
latter will SEGV dereferencing it.
pthread_create() can fail if either the user's ulimit -u or Linux
kernel's /proc/sys/kernel/threads-max is reached.
Choosing to conti
This is enforcing a hard requirement in the spec:
30.1. Feature Requirements
All Vulkan graphics implementations must support the following features:
* robustBufferAccess
On Fri, Nov 8, 2019 at 1:49 PM wrote:
>
> Testing my Vulkan driver agains Vulkan CTS, I am a bit suprised, that is
> seem
Testing my Vulkan driver agains Vulkan CTS, I am a bit suprised, that is seems like CTS does enforce robustBufferAccess (e.g. https://github.com/KhronosGroup/VK-GL-CTS/blob/master/external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp#L1045).
Am I mistaken or can someone explain what the l
