Lines Matching refs:Resolved

962      Resolved.  All stages.
966      Resolved:  Not directly.  But indirectly, probably not in
972      Resolved.  It's here.
977      Resolved:  Yes, with caveats.  In order to provide a global unique
990      Resolved.  Yes, with the same caveats as above.
994      Resolved.  No, implementations are free to support arbitrarily many
1000      Resolved:  Yes.  (It's an increment of zero.  Or a decrement of zero.)
1008      Resolved:  No.  Only by 1.  (Or 0.)
1012      Resolved:  Wrap.  [0,2^32-1]
1016      Resolved:  There is no context state, they must be backed
1021      Resolved:  Not directly, but they may be shared indirectly by sharing the
1026      Resolved.  Yes.  (Note that buffer objects can be shared.
1033      Resolved.  No.  They must be dynamically uniform, similar
1038      Resolved:  Yes, but by providing access to atomic counters.
1044      Resolved:  ARB_shader_atomic_counters.  It's primarily a shader
1051      Resolved:  They should follow the same rules as other shared
1061      Resolved.  There should be a buffer binding (and offset)
1068      Resolved.  We are going to be conservative and make
1073      Resolved.  Yes.  For a single program text, the opaque
1087      Resolved.  Earlier drafts had a traditional indexed get,
1104      Resolved.  THERE IS NO DEFAULT CONTEXT STATE, only the
1111      Resolved.  THERE IS NO DEFAULT CONTEXT STATE.
1117      Resolved.  Undefined.
1121      Resolved.  "atomic_uint" variables are declared as uniforms at global
1127      Resolved.  Yes.
1131      Resolved.  No.  However, layout qualifiers can be used in individual
1137      Resolved.  GetActiveUniformsiv.  Apart from the common type and count
1185      Resolved.  Yes.  One of the intended uses of this programming model is to
1199      Resolved.  <offset> must be a multiple of four.  <size> has no required