mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-24 23:38:10 +02:00
68ab25e6d4
On a7xx, the immediates that get promoted to const registers will be initialized in the preamble instead of being part of the const state. So technically, we won't need the immediate state that is part of the const state anymore on a7xx. However, it is still a convenient place for ir3_cp to store the immediates that should be promoted to const registers before they are lowered to the preamble. This causes one issue: the binning pass isn't allowed to modify the const state while it's perfectly fine for it to use different immediates compared to the non-binning pass on a7xx. Even pre-a7xx this is fine as long as the size of the immediate buffer is the same. To allow the binning pass to modify its immediate state while keeping its const state immutable, this commit moves the fields related to immediates into a new struct. Runtime checks are added to enforce that the size of the immediate buffer is the same for the binning and non-binning variant pre-a7xx. Signed-off-by: Job Noorman <jnoorman@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32454> |
||
|---|---|---|
| .. | ||
| examples | ||
| a4xx.cc | ||
| a6xx.cc | ||
| ir3_asm.cc | ||
| ir3_asm.h | ||
| main.cc | ||
| main.h | ||
| meson.build | ||
| README.rst | ||
Overview ======== Computerator is a tool to launch compute shaders, written in assembly. The main purpose is to have an easy way to experiment with instructions without dealing with the entire compiler stack (which makes controlling the order of instructions, the registers chosen, etc, difficult). The choice of compute shaders is simply because there is far less state setup required. Headers ------- The shader assembly can be prefixed with headers to control state setup: * ``@localsize X, Y, Z`` - configures local workgroup size * ``@buf SZ (cN.c)`` - configures an SSBO of the specified size (in dwords). The order of the ``@buf`` headers determines the index, ie the first ``@buf`` header is ``g[0]``, the second ``g[1]``, and so on. The iova of the buffer is written as a vec2 to ``cN.c`` * ``@const(cN.c)`` configures a const vec4 starting at specified const register, ie ``@const(c1.x) 1.0, 2.0, 3.0, 4.0`` will populate ``c1.xyzw`` with ``vec4(1.0, 2.0, 3.0, 4.0)`` * ``@invocationid(rN.c)`` will populate a vec3 starting at the specified register with the local invocation-id * ``@wgid(rN.c)`` will populate a vec3 starting at the specified register with the workgroup-id (must be a high-reg, ie. ``r48.x`` and above) * ``@numwg(cN.c)`` will populate a vec3 starting at the specified const register Example ------- ``` @localsize 32, 1, 1 @buf 32 ; g[0] @const(c0.x) 0.0, 0.0, 0.0, 0.0 @const(c1.x) 1.0, 2.0, 3.0, 4.0 @wgid(r48.x) ; r48.xyz @invocationid(r0.x) ; r0.xyz @numwg(c2.x) ; c2.xyz mov.u32u32 r0.y, r0.x (rpt5)nop stib.untyped.1d.u32.1 g[0] + r0.y, r0.x end nop ``` Usage ----- ``` cat myshader.asm | ./computerator --disasm --groups=4,4,4 ```