On 08/31/2012 01:37 PM, Vadim Girlin wrote:
> From ARB_sync spec:
>
> If the value of is zero, then ClientWaitSync does not
> block, but simply tests the current state of . TIMEOUT_EXPIRED
> will be returned in this case if is not signaled, even though
> no actual wait was perfor
On Fri, 2012-08-31 at 15:50 -0600, Brian Paul wrote:
> On 08/31/2012 02:53 PM, Eric Anholt wrote:
> > Vadim Girlin writes:
> >
> >> From ARB_sync spec:
> >>
> >> If the value of is zero, then ClientWaitSync does not
> >> block, but simply tests the current state of. TIMEOUT_EXPIRED
> >
On 08/31/2012 02:53 PM, Eric Anholt wrote:
Vadim Girlin writes:
From ARB_sync spec:
If the value of is zero, then ClientWaitSync does not
block, but simply tests the current state of. TIMEOUT_EXPIRED
will be returned in this case if is not signaled, even though
no actua
Vadim Girlin writes:
> From ARB_sync spec:
>
> If the value of is zero, then ClientWaitSync does not
> block, but simply tests the current state of . TIMEOUT_EXPIRED
> will be returned in this case if is not signaled, even though
> no actual wait was performed.
>
> Fixes random
>From ARB_sync spec:
If the value of is zero, then ClientWaitSync does not
block, but simply tests the current state of . TIMEOUT_EXPIRED
will be returned in this case if is not signaled, even though
no actual wait was performed.
Fixes random fails of the arb_sync-timeout-zero p