diff options
author | Kenneth Graunke <[email protected]> | 2015-11-17 00:26:37 -0800 |
---|---|---|
committer | Kenneth Graunke <[email protected]> | 2015-12-22 15:57:59 -0800 |
commit | 7d539080c1a491aff9fb3e90c25df89884477aa8 (patch) | |
tree | 066f321f1cef0a6a1578a4490c63ef9e7d5e1259 /docs/specs/WL_bind_wayland_display.spec | |
parent | 50fc4a925644378c50282004304bc8fd64b95e3c (diff) |
nir: Add a writemask to store intrinsics.
Tessellation control shaders need to be careful when writing outputs.
Because multiple threads can concurrently write the same output
variables, we need to only write the exact components we were told.
Traditionally, for sub-vector writes, we've read the whole vector,
updated the temporary, and written the whole vector back. This breaks
down with concurrent access.
This patch prepares the way for a solution by adding a writemask field
to store_var intrinsics, as well as the other store intrinsics. It then
updates all produces to emit a writemask of "all channels enabled". It
updates nir_lower_io to copy the writemask to output store intrinsics.
Finally, it updates nir_lower_vars_to_ssa to handle partial writemasks
by doing a read-modify-write cycle (which is safe, because local
variables are specific to a single thread).
This should have no functional change, since no one actually emits
partial writemasks yet.
v2: Make nir_validate momentarily assert that writemasks cover the
complete value - we shouldn't have partial writemasks yet
(requested by Jason Ekstrand).
v3: Fix accidental SSBO change that arose from merge conflicts.
v4: Don't try to handle writemasks in ir3_compiler_nir - my code
for indirects was likely wrong, and TTN doesn't generate partial
writemasks today anyway. Change them to asserts as requested by
Rob Clark.
Signed-off-by: Kenneth Graunke <[email protected]>
Reviewed-by: Jason Ekstrand <[email protected]> [v3]
Diffstat (limited to 'docs/specs/WL_bind_wayland_display.spec')
0 files changed, 0 insertions, 0 deletions