I have a similar patch locally on my machine.
s/list/set in the very last comment in the patch and it is:
Reviewed-by: Thomas Helland
There are also similar situations in other areas where we can
do the same trick. Constant propagation I believe?
Afk, so can't check what other passes I looked at
Previously each time we saw a variable we just created a duplicate
entry in the list. This is particularly bad for loops were we add
everything twice, and then throw nested loops into the mix and the
list was growing expoentially.
This stops the glsl-vs-unroll-explosion test which has 16 nested
lo
