Lines Matching refs:critical

80     a critical section of fragment shader code.  For pairs of shader
82     implementation will guarantee that the critical section of the fragment
88     exclusion in the critical section for any pair of fragments corresponding
97     guarantees that the critical section for multiple shader invocations with
106     extension can access such data structures in the critical section without
172     endInvocationInterlockARB() allow shaders to specify a critical section,
192     qualifier, the interlock will ensure that the critical sections of
199     layout qualifier, the critical sections of invocations X and Y with
202     considered to precede fragment B, the critical section of invocation X is
203     guaranteed to complete before the critical section of invocation Y begins.
221     If fragment shader X completes its critical section before fragment shader
222     Y begins its critical section, all stores to memory performed in the
223     critical section of invocation X using a pointer, image uniform, atomic
226     critical section of invocation Y.
279       their critical sections concurrently.  This could cause problems for
285       critical section concurrently.  If a separate set of data structures is
286       provided for each sample, no conflicts should occur within the critical
305       qualifiers, the critical section for one fragment must wait until the
306       critical section for the other fragment completes.
313       performance, since the critical section implementation doesn't need to
315       completed their critical sections.  Some algorithms (e.g., building data
324       RESOLVED:  Yes, fragment shaders with critical sections may still write
353         critical section, what operations (if any) must be performed in shader
370       performed inside the critical section, and the use of "coherent" ensures
374         critical section?  Or should we just automatically infer a critical
376         fragment shader in a critical section?
378       RESOLVED:  Provide an explicit critical section.
380       We definitely don't want to wrap the entire shader in a critical section
387       smaller critical section reduces the amount of time other fragments are
389       conflicting fragments before they hit the critical section.
391       While a compiler could analyze the code and wrap a critical section
395       explicitly identify a critical section doesn't seem overwhelmingly
401         delimiting a critical section?
405       shader using this functionality has a single critical section that can
413       deal with unusual cases (like entering a critical section and never
414       leaving, leaving a critical section without entering it, or trying to
415       enter a critical section more than once).