Skip to content

nir: Keep track of cross-invocation mesh shader output access.

Timur Kristóf requested to merge Venemo/mesa:nir_mesh_cross_invocation into main

On some implementations eg. AMD RDNA2 the driver can generate a more optimal code path knowing whether outputs are indexed using the local invocation index or not.

If an output is only indexed by the local invocation index, it can stay in a variable (register), otherwise it has to be stored to memory and loaded at the end of the shader.

Merge request reports