mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-05 07:28:11 +02:00
nir: keep the phi order when splitting blocks
All things being equal is better to keep the original order. Since the new block is empty, push the phis in order to tail. Reviewed-by: Jason Ekstrand <jason@jlekstrand.net> Reviewed-by: Daniel Schürmann <daniel.schuermann@campus.tu-berlin.de>
This commit is contained in:
parent
38f542783f
commit
51547bbc5a
1 changed files with 2 additions and 3 deletions
|
|
@ -195,8 +195,7 @@ split_block_beginning(nir_block *block)
|
|||
}
|
||||
|
||||
/* Any phi nodes must stay part of the new block, or else their
|
||||
* sourcse will be messed up. This will reverse the order of the phis, but
|
||||
* order shouldn't matter.
|
||||
* sources will be messed up.
|
||||
*/
|
||||
nir_foreach_instr_safe(instr, block) {
|
||||
if (instr->type != nir_instr_type_phi)
|
||||
|
|
@ -204,7 +203,7 @@ split_block_beginning(nir_block *block)
|
|||
|
||||
exec_node_remove(&instr->node);
|
||||
instr->block = new_block;
|
||||
exec_list_push_head(&new_block->instr_list, &instr->node);
|
||||
exec_list_push_tail(&new_block->instr_list, &instr->node);
|
||||
}
|
||||
|
||||
return new_block;
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue