diff options
author | Kenneth Graunke <[email protected]> | 2014-05-30 16:41:32 -0700 |
---|---|---|
committer | Kenneth Graunke <[email protected]> | 2014-06-02 15:09:30 -0700 |
commit | 776ad51165b1f7ee18a9a4cccbed1ce3b2c4fcf9 (patch) | |
tree | 2cad3bd54226334a771c8f8a18453f27a0ab480e /src/mesa/drivers/dri/i965/brw_clip_tri.c | |
parent | ff340ce3c3326959027d7cb9a611c6fab1d89941 (diff) |
i965: Don't use brw_set_conditionalmod in the FS and vec4 compilers.
brw_set_conditionalmod and brw_next_insn work together to set the
conditional modifier for the next instruction, then turn it off.
The Gen8+ generators don't implement this: we just set it for all future
instructions, and whack it for each fs_inst/vec4_instruction.
Both approaches work out because we only set conditional_mod on
IR instructions like CMP, AND, and so on, which correspond to exactly
one assembly instruction. The Gen8 generators would break if we had
an IR instruction that generated multiple instructions, and the Gen4-7
EU emit layer would do...something.
To safeguard against this, assert that we only generated one instruction
if conditional_mod is set, and just set the flag directly on that
instruction rather than altering default state.
Signed-off-by: Kenneth Graunke <[email protected]>
Reviewed-by: Matt Turner <[email protected]>
Diffstat (limited to 'src/mesa/drivers/dri/i965/brw_clip_tri.c')
0 files changed, 0 insertions, 0 deletions