summaryrefslogtreecommitdiffstats
path: root/src/gallium/drivers/vc5/vc5_context.h
diff options
context:
space:
mode:
authorEric Anholt <[email protected]>2018-03-21 15:07:19 -0700
committerEric Anholt <[email protected]>2018-03-26 17:46:19 -0700
commit33878641305345b9bb76ad5ebf2335ec9c17adfa (patch)
treec423a617c529008c2ee0d7f720726d9d4176fcfc /src/gallium/drivers/vc5/vc5_context.h
parent09ac5ade8f3855e42e4902d7e1acab540f3f1568 (diff)
broadcom/vc5: Fix transform feedback in the presence of point size.
I had this note to myself, and it turns out that a lot of CTS tests use XFB with points to get data out without using a fragment shader. Keep track of two sets of precomputed TF specs (point size in VPM prologue or not), and switch between them when we enable/disable point size.
Diffstat (limited to 'src/gallium/drivers/vc5/vc5_context.h')
-rw-r--r--src/gallium/drivers/vc5/vc5_context.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gallium/drivers/vc5/vc5_context.h b/src/gallium/drivers/vc5/vc5_context.h
index 976fba90f81..7272e045c4f 100644
--- a/src/gallium/drivers/vc5/vc5_context.h
+++ b/src/gallium/drivers/vc5/vc5_context.h
@@ -131,6 +131,7 @@ struct vc5_uncompiled_shader {
uint32_t num_tf_outputs;
struct v3d_varying_slot *tf_outputs;
uint16_t tf_specs[16];
+ uint16_t tf_specs_psiz[16];
uint32_t num_tf_specs;
/**