diff options
| author | Erico Nunes <[email protected]> | 2020-01-12 14:30:26 +0100 |
|---|---|---|
| committer | Marge Bot <[email protected]> | 2020-01-15 22:55:31 +0000 |
| commit | 7e2765fded33ed13693939b0e4ef94943fedf2cb (patch) | |
| tree | 4d36e3a7d67fa2f5ff0662254e8a7c1ccda4cf61 /src/util/format_rgb9e5.h | |
| parent | a3a73d116c1425d1d2da2f3b3aabe06a53c3d800 (diff) | |
lima/ppir: remove orphan load node after cloning
There are some cases in shades using control flow where the varying load
is cloned to every block, and then the original node is left orphan.
This is not harmful for program execution, but it complicates analysis
for register allocation as there is now a case of writing to a register
that is never read.
While ppir doesn't have a dead code elimination pass for its own
optimizations and it is not hard to detect when we cloned the last load,
let's remove it early.
Signed-off-by: Erico Nunes <[email protected]>
Reviewed-by: Vasily Khoruzhick <[email protected]>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3358>
Diffstat (limited to 'src/util/format_rgb9e5.h')
0 files changed, 0 insertions, 0 deletions