From d29435e7cb3f8a9ef369c90ff890c018463890a7 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Mon, 23 Jul 2018 13:30:58 -0700 Subject: v3d: Track the buffers being loaded separately. We were computing this at RCL generation time, but that means you can't unflag the store for an invalidate_resource, or not flag the store if writmasking is disabled. --- src/gallium/drivers/v3d/v3d_context.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/gallium/drivers/v3d/v3d_context.h') diff --git a/src/gallium/drivers/v3d/v3d_context.h b/src/gallium/drivers/v3d/v3d_context.h index 1f1b3d0edea..b61dacf66c7 100644 --- a/src/gallium/drivers/v3d/v3d_context.h +++ b/src/gallium/drivers/v3d/v3d_context.h @@ -281,6 +281,10 @@ struct v3d_job { * first rendering. */ uint32_t clear; + /* Bitmask of PIPE_CLEAR_* of buffers that have been read by a draw + * call without having been cleared first. + */ + uint32_t load; /* Bitmask of PIPE_CLEAR_* of buffers that have been rendered to * (either clears or draws) and should be stored. */ -- cgit v1.2.3