projects / mesa.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e1385e8) | patch
v3d: Fix up VS output setup during precompiles.
authorEric Anholt <eric@anholt.net>
Thu, 3 Jan 2019 06:48:29 +0000 (22:48 -0800)
committerEric Anholt <eric@anholt.net>
Fri, 4 Jan 2019 23:41:23 +0000 (15:41 -0800)
commitf8e6b364b0aa64f0935a232574536dc462257418
tree15d54b0095dbb3d5eeb529c6e1e463cbcbd985a4tree
parente1385e879d5b6e80dc5572eb987ef773431fba27commit | diff
v3d: Fix up VS output setup during precompiles.

I noticed that a VS I was debugging was missing all of its output stores
-- outputs_written was for POS, VAR0, VAR3, while the shader's variables
were POS, VAR9, and VAR12.  I'm not sure what outputs_written is supposed
to be doing here, but we can just walk the declared variables and avoid
both this bug and the emission of extra stvpms for less-than-vec4
varyings.
src/gallium/drivers/v3d/v3d_program.c diff | blob | history