freedreno/a3xx: fix const confusion
authorRob Clark <robclark@freedesktop.org>
Tue, 14 Jan 2014 14:54:02 +0000 (09:54 -0500)
committerRob Clark <robclark@freedesktop.org>
Sat, 1 Feb 2014 16:57:09 +0000 (11:57 -0500)
commit98c1111462f13cee705d5c0bd89f9bab510f299f
tree1da1ca4ab63f8dbff72ece152a3e265c8b6d9611
parent5c6961efae7d2baa224580af45f8d8968dda3a67
freedreno/a3xx: fix const confusion

Gallium can leave const buffers bound above what is used by the current
shader.  Which can have a couple bad effects:

1) write beyond const space assigned, which can trigger HLSQ lockup
2) double emit of immed consts, first with bound const buffer vals
followed by with actual immed vals.  This seems to be a sort of
undefined condition.

Signed-off-by: Rob Clark <robclark@freedesktop.org>
src/gallium/drivers/freedreno/a3xx/fd3_compiler.c
src/gallium/drivers/freedreno/a3xx/fd3_emit.c