i965: Don't do legacy userclipping in non-compatibility contexts.
authorKenneth Graunke <kenneth@whitecape.org>
Fri, 28 Aug 2015 08:43:23 +0000 (01:43 -0700)
committerKenneth Graunke <kenneth@whitecape.org>
Fri, 4 Sep 2015 05:31:04 +0000 (22:31 -0700)
commitfba4823a916b63f279955dbe6d98b6efc666f53e
tree3128b1ff79fed9f59d2cb6a057a1df197c539690
parent4f4b7c4711d98606270133dfd456acabfa8267a6
i965: Don't do legacy userclipping in non-compatibility contexts.

According to the GLSL 1.50 specification, page 76:
"The shader must also set all values in gl_ClipDistance that have been
 enabled via the OpenGL API, or results are undefined."

With this patch, we only enable clip distance writes when the shader
actually writes them.  We no longer force a value to be written when
clip planes are enabled in the API.  This could mean the first varying
slot would be used as clip distances - I believe it should be the safe
kind of undefined behavior.

Empirically, it doesn't seem to cause a problem.

Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
src/mesa/drivers/dri/i965/brw_vs.c