From cc97b6a34a81e58c29bed6dae06613b388506283 Mon Sep 17 00:00:00 2001 From: Samuel Pitoiset Date: Tue, 28 Jun 2016 00:59:46 +0200 Subject: [PATCH] gm107/ir: make sure that flagsDef is set when emitting setcond Rely on the existence of a second destination when emitting a setcond flag is dangerous, because this doesn't mean that the flag has been correctly set. Instead rely on flagsDef like what emitX() does for flagsSrc. Signed-off-by: Samuel Pitoiset Reviewed-by: Ilia Mirkin Cc: --- src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp index 40afbce9c6f..2c5e8f69d13 100644 --- a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp +++ b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp @@ -420,7 +420,7 @@ CodeEmitterGM107::emitSAT(int pos) void CodeEmitterGM107::emitCC(int pos) { - emitField(pos, 1, insn->defExists(1)); + emitField(pos, 1, insn->flagsDef >= 0); } void -- 2.30.2