st/mesa: report correct precision information for low/medium/high ints
authorIlia Mirkin <imirkin@alum.mit.edu>
Sun, 20 Mar 2016 03:27:56 +0000 (23:27 -0400)
committerIlia Mirkin <imirkin@alum.mit.edu>
Sun, 20 Mar 2016 21:51:08 +0000 (17:51 -0400)
commitbbbdcdcf75f05f97ea346fd6d84ecc3d8ec61d24
tree58e9243bc1a5040aa575804bef929e5267222676
parenteeb117a09d6c0eb2b4fa94d55e8015c8aa982727
st/mesa: report correct precision information for low/medium/high ints

When we have native integers, these have full precision. Whether they're
low/medium/high isn't piped through the TGSI yet, but eventually those
might have differing precisions. For now they're just 32-bit ints.

Fixes the following dEQP tests:

  dEQP-GLES3.functional.state_query.shader.precision_vertex_highp_int
  dEQP-GLES3.functional.state_query.shader.precision_fragment_highp_int

which expected highp ints to have full 32-bit precision, not the default
23-bit float precision.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Dave Airlie <airlied@redhat.com>
src/mesa/state_tracker/st_extensions.c