Lines Matching refs:critical

80     critical section of fragment shader code.  For pairs of shader invocations
82     will guarantee that the critical section of the fragment shader will be
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
176     endInvocationInterlockNV() allow shaders to specify a critical section,
196     qualifier, the interlock will ensure that the critical sections of
203     layout qualifier, the critical sections of invocations X and Y with
206     considered to precede fragment B, the critical section of invocation X is
207     guaranteed to complete before the critical section of invocation Y begins.
225     If fragment shader X completes its critical section before fragment shader
226     Y begins its critical section, all stores to memory performed in the
227     critical section of invocation X using a pointer, image uniform, atomic
230     critical section of invocation Y.
338     "NV_sample_interlock_ordered" options, it will configure a critical
340     (fragment shader interlock end) opcodes.  The execution of the critical
357     The FSIB instruction specifies the beginning of a critical section in a
358     fragment program, where execution of the critical section is ordered
373     The FSIE instruction specifies the end of a critical section in a fragment
374     program, where execution of the critical section is ordered relative to
392       identify a critical section during which other invocations with
393       overlapping coverage are locked out until the critical section
407       their critical sections concurrently.  This could cause problems for
413       critical section concurrently.  If a separate set of data structures is
414       provided for each sample, no conflicts should occur within the critical
433       qualifiers, the critical section for one fragment must wait until the
434       critical section for the other fragment completes.
441       performance, since the critical section implementation doesn't need to
443       completed their critical sections.  Some algorithms (e.g., building data
452       RESOLVED:  Yes, fragment shaders with critical sections may still write
481         critical section, what operations (if any) must be performed in shader
498       performed inside the critical section, and the use of "coherent" ensures
502         critical section?  Or should we just automatically infer a critical
504         fragment shader in a critical section?
506       RESOLVED:  Provide an explicit critical section.
508       We definitely don't want to wrap the entire shader in a critical section
515       smaller critical section reduces the amount of time other fragments are
517       conflicting fragments before they hit the critical section.
519       While a compiler could analyze the code and wrap a critical section
523       explicitly identify a critical section doesn't seem overwhelmingly
529         delimiting a critical section?
533       shader using this functionality has a single critical section that can
541       deal with unusual cases (like entering a critical section and never
542       leaving, leaving a critical section without entering it, or trying to
543       enter a critical section more than once).