Commented out apparently-bogus validity check.

MOD_SATURATE is showing up in pixel shaders generated from Microsoft's HLSL compiler, so either I misread the spec when I thought this modifier was vertex-shader-specific, or the spec is wrong. Will check later. --HG-- branch : trunk
icculus · Apr 19, 2008 · 80fa232 · 80fa232
1 parent 41763c9
commit 80fa232
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/mojoshader.c b/mojoshader.c
@@ -2951,11 +2951,15 @@ static int parse_destination_token(Context *ctx, DestArgInfo *info)
             return fail(ctx, "Result shift scale isn't 1 to 3, or 13 to 15.");
     } // if
 
+    // !!! FIXME: these are definitely showing up in valid pixel shaders.
+    // !!! FIXME:  go re-read the spec on this one.
+    #if 0
     if (info->result_mod & MOD_SATURATE)  // Saturate (vertex shaders only)
     {
         if (ctx->shader_type != MOJOSHADER_TYPE_VERTEX)
             return fail(ctx, "Saturate result mod in non-vertex shader");
     } // if
+    #endif
 
     if (info->result_mod & MOD_PP)  // Partial precision (pixel shaders only)
     {