Lines Matching refs:ClientWaitSync

104     enum ClientWaitSync(sync sync,bitfield flags,uint64 timeout)
137     Accepted in the <flags> parameter of ClientWaitSync:
145     Returned by ClientWaitSync:
205     any ClientWaitSync or WaitSync commands (see below) blocking on
253     completed, or if no ClientWaitSync or WaitSync commands are blocking
257     ClientWaitSync or WaitSync command. In either case, after returning
271         enum ClientWaitSync(sync sync,bitfield flags,uint64 timeout)
280     If <sync> is signaled at the time ClientWaitSync is called
281     then ClientWaitSync returns immediately. If <sync> is unsignaled at
282     the time ClientWaitSync is called then ClientWaitSync will block and
287     ClientWaitSync returns one of four status values. A return value of
289     ClientWaitSync was called. ALREADY_SIGNALED will always be returned
295     generating a GL error as specified below, ClientWaitSync immediately
298     If the value of <timeout> is zero, then ClientWaitSync does not
311     is similar to ClientWaitSync, but instead of blocking and not
322     <sync> has the same meaning as for ClientWaitSync.
345     in a ClientWaitSync command, the GL server to be blocked as the
365     but not yet flushed to the graphics pipeline), then ClientWaitSync
368     unsignaled when ClientWaitSync is called, then the equivalent of
379     on that object in a ClientWaitSync command, or a GL server is
503     ClientWaitSync or WaitSync commands. Once any corresponding fence
578     ClientWaitSync, SignalSync, WaitSync, or GetSynciv is not the name
588     ClientWaitSync contains bits other than SYNC_FLUSH_COMMANDS_BIT, or
743         RESOLVED: ClientWaitSync and FenceSync are not display listable.
744         ClientWaitSync is defined to block the application, not the
944         R7) A wait function, such as ClientWaitSync or WaitSync, waits
954         B1) Calling ClientWaitSync with a timeout of 0 will return TRUE
956             calling ClientWaitSync with a timeout of 0 in a loop can
962         B3) ClientWaitSync could take a timeout parameter and return a
963             boolean. If the timeout period has expired, ClientWaitSync
965             ClientWaitSync unblocks because the sync object it was
1033             ClientWaitSync(syncObjectA);
1042             // ClientWaitSync issued above will unblock and allow B
1051         RESOLVED: ClientWaitSync for blocking on the client side.
1297     Version 12, 2006/03/31 - Changed FinishSync to ClientWaitSync. Note
1298     that ClientWaitSync behavior is explicitly undefined (and note
1314     value returned from ClientWaitSync when the sync was signaled at
1387         returned even when ClientWaitSync is called with a
1393         ClientWaitSync and WaitSync to GLbitfield.