Module: Mesa Branch: master Commit: 16d493f1e7a58e8e1f6e665ac5e21f1b35b1f8f1 URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=16d493f1e7a58e8e1f6e665ac5e21f1b35b1f8f1
Author: Rob Clark <[email protected]> Date: Wed Apr 12 11:47:22 2017 -0400 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 <[email protected]> Reviewed-by: Marek Olšák <[email protected]> Reviewed-by: Nicolai Hähnle <[email protected]> --- src/gallium/docs/source/tgsi.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/gallium/docs/source/tgsi.rst b/src/gallium/docs/source/tgsi.rst index f68d349a48..89acb521ce 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. _______________________________________________ mesa-commit mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-commit
