i965: Remove brw_set_predicate_inverse(p, true) from scratch offset code

Given that it exists between a push/pop of instruction state, this call
can only affect the MOV or ADD instruction generated just below it.
Neither of those instructions are predicated, so it makes no sense to
ask for the inverse predicate.

This fixes grumblings from the simulator debugger, which was
complaining about an invalid predicate.

Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Paul Berry <stereotype441@gmail.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
This commit is contained in:
Kenneth Graunke 2012-09-20 16:31:15 -07:00
parent 328961d955
commit cd49025aff

View file

@ -521,7 +521,6 @@ vec4_visitor::generate_oword_dual_block_offsets(struct brw_reg m1,
brw_MOV(p, m1_0, index_0);
brw_set_predicate_inverse(p, true);
if (index.file == BRW_IMMEDIATE_VALUE) {
index_4.dw1.ud += second_vertex_offset;
brw_MOV(p, m1_4, index_4);