Lines Matching refs:availability

124 Two memory accesses through distinct references may: require availability
289 <<memory-model-availability-visibility,availability and visibility
375 The memory semantics operand can: also include availability and visibility
376 flags, which apply availability and visibility operations as described in
377 <<memory-model-availability-visibility,availability and visibility>>.
378 The availability/visibility flags are:
381     Performs an availability operation before the release operation or
387 <<memory-model-availability-visibility-semantics,Availability and Visibility
515 not perform implicit availability or visibility operations.
518 <<memory-model-instruction-av-vis,per-instruction availability and
627 Additional <<memory-model-availability-visibility,availability and
643 [[memory-model-availability-visibility]]
717 shader-based availability/visibility operations, in other cases writes can
726   * For an availability operation, the source scope is a set of
741 Recall that availability and visibility states are per-memory location, and
746 An availability operation AV that happens-after W and that includes (A,R,L)
768 An _availability chain_ is a sequence of availability operations to
772 An example is an availability operation with destination scope of the
773 workgroup instance domain that happens-before an availability operation to
775 An availability chain AVC that happens-after W and that includes (A,R,L) in
778 An availability chain with a single element is just the availability
794 [[memory-model-vulkan-availability-visibility]]
797 The following operations generate availability, visibility, and domain
799 When multiple availability/visibility/domain operations are described, they
808   * An availability operation with source scope of all writes in the first
817 flink:vkFlushMappedMemoryRanges performs an availability operation, with a
831 [[memory-model-availability-visibility-semantics]]
835 in its semantics performs an availability operation whose source scope
839 The implicit availability operation is program-ordered between the barrier
864   * code:Invocation perform no availability/visibility operations.
866 When an availability operation performed by an agent A includes a memory
877 write instruction that includes MakeTexelAvailable, performs an availability
881 operand specified in <<memory-model-availability-visibility-semantics,
883 The implicit availability operation is program-ordered between the write and
889 as specified in <<memory-model-availability-visibility-semantics,
916 processor with the same path to memory, and thus availability and visibility
939   ** NOTE: this case means no availability/visibility ops are required when
948   ** X is a write, Y is a write, AVC(A~X~,R~X~,D,L) is an availability chain
950   ** X is a write, Y is a read, AVC(A~X~,R~X~,D,L) is an availability chain
1152 This memory model allows memory accesses with and without availability and
1160 instruction as having optional implicit availability/visibility operations.
1165 Atomic operations implicitly have availability/visibility operations, and