[PATCH]: Fix PR tree-optimization/19038

[Daniel Berlin]

On Fri, 2005-01-21 at 15:25 -0500, Diego Novillo wrote:
> Daniel Berlin wrote:
> 
> > loop-im would have hoisted it if it was profitable, and then we'd have
> > copy-proped that version in dom3.
> > 
> OK, so it's what I thought.  We create a dependency on code hoisting. 
> Not a big problem,  I guess, but the comment is misleading.
> 
> Rather say something like: Do not propagate copies, if the propagated 
> value is at a deeper loop depth.  This may move loop variant variables 
> outside of their loops and prevent coalescing opportunities.  If the 
> value was loop invariant, it will be hoisted by LICM and exposed for 
> copy propagation.

Okay with that change?