> Since this copy_propagation_state covers just the acp and not the kills
> list (whcih is still part of the copy propagation state in the visitor
> class), could we call it "acp"?
I'm considering moving the kills list inside that state, hence the
more general name.
> > @@ -191,26 +283,21 @@
>
Caio Marcelo de Oliveira Filho writes:
> Separate higher level logic of visiting instructions and chosing when
> to store and use new copy data from the datastructure holding the copy
> propagation information. This will also make easier later patches that
> change the structure.
> ---
>
Separate higher level logic of visiting instructions and chosing when
to store and use new copy data from the datastructure holding the copy
propagation information. This will also make easier later patches that
change the structure.
---
.../glsl/opt_copy_propagation_elements.cpp| 269
