i965/fs: Do dead code elimination just after copy propagation.
If we put the register coalescing in between the two, then we end up with code sequences involving dead writes that the dead code elimination doesn't know how to remove. In place of making dead code elimination smart (which we should do, too), make it less important for the moment. shader-db results: total instructions in shared programs: 722240 -> 721275 (-0.13%) instructions in affected programs: 50573 -> 49608 (-1.91%) (no shaders regressed). Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
This commit is contained in:
@@ -1925,10 +1925,10 @@ fs_visitor::run()
|
||||
progress = opt_algebraic() || progress;
|
||||
progress = opt_cse() || progress;
|
||||
progress = opt_copy_propagate() || progress;
|
||||
progress = dead_code_eliminate() || progress;
|
||||
progress = register_coalesce() || progress;
|
||||
progress = register_coalesce_2() || progress;
|
||||
progress = compute_to_mrf() || progress;
|
||||
progress = dead_code_eliminate() || progress;
|
||||
} while (progress);
|
||||
|
||||
remove_dead_constants();
|
||||
|
||||
Reference in New Issue
Block a user