i965: Set correct values for range/precision of fragment shader types

diff --git a/src/mesa/drivers/dri/i965/brw_context.c b/src/mesa/drivers/dri/i965/brw_context.c
index 8fc322fd82edb9996ee0db66f282a4bbd19696b8..d3b61abe89676276991c3150c0122fc26bb8fe07 100644 (file)
--- a/src/mesa/drivers/dri/i965/brw_context.c
+++ b/src/mesa/drivers/dri/i965/brw_context.c
@@ -151,6 +151,15 @@ GLboolean brwCreateContext( int api,
       MIN2(ctx->Const.FragmentProgram.MaxNativeParameters,
           ctx->Const.FragmentProgram.MaxEnvParams);
 
+   /* Fragment shaders use real, 32-bit twos-complement integers for all
+    * integer types.
+    */
+   ctx->FragmentProgram.LowInt.RangeMin = 31;
+   ctx->FragmentProgram.LowInt.RangeMax = 30;
+   ctx->FragmentProgram.LowInt.Precision = 0;
+   ctx->FragmentProgram.HighInt = ctx->FragmentProgram.MediumInt
+      = ctx->FragmentProgram.LowInt;
+
    /* Gen6 converts quads to polygon in beginning of 3D pipeline,
       but we're not sure how it's actually done for vertex order,
       that affect provoking vertex decision. Always use last vertex