nv50/ir: clean up saturated values immediately
Since we don't iterate to a fixed point, we can end up in situations
where we have a SAT instruction + a long immediate. This is not legal.
However since it's immediately computable, just run unary straight away
to handle the situation.
Fixes: 24a799ad35
("nv50/ir: fix ConstantFolding with saturation")
Reported-by: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: mesa-stable@lists.freedesktop.org
This commit is contained in:
parent
ea22ac23e0
commit
165e18dd21
|
@ -727,7 +727,9 @@ ConstantFolding::expr(Instruction *i,
|
|||
// Leave PFETCH alone... we just folded its 2 args into 1.
|
||||
break;
|
||||
default:
|
||||
i->op = i->saturate ? OP_SAT : OP_MOV; /* SAT handled by unary() */
|
||||
i->op = i->saturate ? OP_SAT : OP_MOV;
|
||||
if (i->saturate)
|
||||
unary(i, *i->getSrc(0)->asImm());
|
||||
break;
|
||||
}
|
||||
i->subOp = 0;
|
||||
|
@ -1513,8 +1515,11 @@ ConstantFolding::opnd(Instruction *i, ImmediateValue &imm0, int s)
|
|||
// This can get left behind some of the optimizations which simplify
|
||||
// saturatable values.
|
||||
if (newi->op == OP_MOV && newi->saturate) {
|
||||
ImmediateValue tmp;
|
||||
newi->saturate = 0;
|
||||
newi->op = OP_SAT;
|
||||
if (newi->src(0).getImmediate(tmp))
|
||||
unary(newi, tmp);
|
||||
}
|
||||
|
||||
if (newi->op != op)
|
||||
|
|
Loading…
Reference in New Issue