v3d: Disable shader-db cycle estimates until we sort out TMU estimates.
authorEric Anholt <eric@anholt.net>
Mon, 16 Jul 2018 20:57:03 +0000 (13:57 -0700)
committerEric Anholt <eric@anholt.net>
Mon, 16 Jul 2018 21:39:59 +0000 (14:39 -0700)
I keep having to ignore these shader-db changes since I don't trust them,
so just disable the reports entirely.

src/broadcom/compiler/vir_to_qpu.c

index 83b1936cbd9d76b5bc91b6bb21e55e6b33776c7a..2c0349bb3b77704344d67f9cb508363d22263d8e 100644 (file)
@@ -405,7 +405,10 @@ v3d_vir_to_qpu(struct v3d_compile *c, struct qpu_reg *temp_registers)
                         c->qpu_inst_count);
         }
 
-        if (V3D_DEBUG & V3D_DEBUG_SHADERDB) {
+        /* The QPU cycle estimates are pretty broken (see waddr_latency()), so
+         * don't report them for now.
+         */
+        if (false) {
                 fprintf(stderr, "SHADER-DB: %s prog %d/%d: %d estimated cycles\n",
                         vir_get_stage_name(c),
                         c->program_id, c->variant_id,