From: Rob Clark Date: Wed, 12 Apr 2017 15:47:22 +0000 (-0400) Subject: gallium/docs: small correction about register files for atomics X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=16d493f1e7a58e8e1f6e665ac5e21f1b35b1f8f1;p=mesa.git gallium/docs: small correction about register files for atomics These can operate on MEMORY[], in addition to BUFFER[] and IMAGE[] Signed-off-by: Rob Clark Reviewed-by: Marek Olšák Reviewed-by: Nicolai Hähnle --- diff --git a/src/gallium/docs/source/tgsi.rst b/src/gallium/docs/source/tgsi.rst index f68d349a485..89acb521ced 100644 --- a/src/gallium/docs/source/tgsi.rst +++ b/src/gallium/docs/source/tgsi.rst @@ -2553,6 +2553,8 @@ after lookup. Resource Access Opcodes ^^^^^^^^^^^^^^^^^^^^^^^ +For these opcodes, the resource can be a BUFFER, IMAGE, or MEMORY. + .. opcode:: LOAD - Fetch data from a shader buffer or image Syntax: ``LOAD dst, resource, address`` @@ -2704,8 +2706,8 @@ These opcodes provide atomic variants of some common arithmetic and logical operations. In this context atomicity means that another concurrent memory access operation that affects the same memory location is guaranteed to be performed strictly before or after the -entire execution of the atomic operation. The resource may be a buffer -or an image. In the case of an image, the offset works the same as for +entire execution of the atomic operation. The resource may be a BUFFER, +IMAGE, or MEMORY. In the case of an image, the offset works the same as for ``LOAD`` and ``STORE``, specified above. These atomic operations may only be used with 32-bit integer image formats.