i965: Drop assert about number of uniforms in ARB handling.
authorKenneth Graunke <kenneth@whitecape.org>
Mon, 15 Oct 2018 16:29:06 +0000 (09:29 -0700)
committerKenneth Graunke <kenneth@whitecape.org>
Mon, 15 Oct 2018 17:56:12 +0000 (10:56 -0700)
My recent prog_to_nir patch started making new sampler uniforms, which
apparently increased the number of parameters.  We used to poke at the
one parameter directly, making it important that there was only one,
but we haven't done that in a while.  It should be safe to just delete
the assertion.

Fixes: 1c0f92d8a8c "nir: Create sampler variables in prog_to_nir."
Reviewed-by: Jason Ekstrand <jason@jlekstrand.net>
src/mesa/drivers/dri/i965/brw_nir_uniforms.cpp

index 35416a74b9c0ca9bd64caa540f0cd254c669341c..66cdc1a10b6266393bedd22d211e4da9e8ae5eaf 100644 (file)
@@ -246,10 +246,9 @@ brw_nir_setup_arb_uniforms(void *mem_ctx, nir_shader *shader,
    stage_prog_data->param = rzalloc_array(mem_ctx, uint32_t, nr_params);
 
    /* For ARB programs, prog_to_nir generates a single "parameters" variable
-    * for all uniform data.  nir_lower_wpos_ytransform may also create an
-    * additional variable.
+    * for all uniform data.  There may be additional sampler variables, and
+    * an extra uniform from nir_lower_wpos_ytransform.
     */
-   assert(shader->uniforms.length() <= 2);
 
    for (unsigned p = 0; p < plist->NumParameters; p++) {
       /* Parameters should be either vec4 uniforms or single component