This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH]: Fix PR tree-optimization/19038
Daniel Berlin wrote:
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.
loop-im would have hoisted it if it was profitable, and then we'd have
copy-proped that version in dom3.
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