From 229836fb379eea6fb34c31410203082e822f3213 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Mon, 16 Jul 2018 13:57:03 -0700 Subject: [PATCH] v3d: Disable shader-db cycle estimates until we sort out TMU estimates. 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 | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/broadcom/compiler/vir_to_qpu.c b/src/broadcom/compiler/vir_to_qpu.c index 83b1936cbd9..2c0349bb3b7 100644 --- a/src/broadcom/compiler/vir_to_qpu.c +++ b/src/broadcom/compiler/vir_to_qpu.c @@ -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, -- 2.30.2