Lines Matching full:operations

16   memory operations to be reordered across ``acquire`` or ``release``
17   operations.
67     Tags can also be organised in lists to allow operations
87     Both synchronizing operations and memory operations can have
143     other operations is target dependent.
167     only synchronize with operations happening in ``addrspace(0)``.
205 ``VulkanMemoryModel``, where synchronizing operations only affect
206 memory operations that specify ``NonPrivatePointer`` semantics.
232 No such relation can be inferred about operations ``B`` and ``C``.
238    Whether ``vulkan:nonprivate`` would be specified on atomic operations is
245 Operations marked with ``vulkan:private`` effectively opt out of the
247 with every synchronizing operation. Note that SPIRV operations that
277 where all memory operations are cached, and the entire cache is
280 operations marked ``NonPrivatePointer`` should not be cached, and the
287 - For memory operations:
289   - Operations with ``vulkan:nonprivate`` should bypass the cache.
290   - Operations with ``vulkan:private`` should be cached.
291   - Operations that specify neither or both should conservatively
294 - For synchronizing operations:
296   - Operations with ``vulkan:nonprivate`` should not flush or
298   - Operations with ``vulkan:private`` should flush or invalidate the cache.
299   - Operations that specify neither or both should conservatively
337 In the above figure, ``X`` and ``Y`` are atomic operations on a
340 space. But no such statement can be made about operations ``A`` and
347 Languages such as OpenCL C provide fence operations such as
427 Combining Operations
430 If a pass can combine multiple memory or synchronizing operations
447 aggressively combine/reorder operations should only combine