Re: RFC: missed loop optimizations from loop induction variable copies

2009-09-23 Thread Zdenek Dvorak
Hi, > IVOpts cannot identify start_26, start_4 and ivtmp_32_7 to be copies. > The root cause is that expression 'i + start' is identified as a common > expression between the test in the header and the index operation in the > latch. This is unified by copy propagation or FRE prior to loop > opt

Re: RFC: missed loop optimizations from loop induction variable copies

2009-09-22 Thread Richard Guenther
On Tue, Sep 22, 2009 at 1:52 PM, Rahul Kharche wrote: > The following causes missed loop optimizations in O2 from creating > unnecessary loop induction variables. Or, is a case of IV opts not > able to coalesce copies of induction variables. A previous post related > to this was made in PR41026 wh

RFC: missed loop optimizations from loop induction variable copies

2009-09-22 Thread Rahul Kharche
The following causes missed loop optimizations in O2 from creating unnecessary loop induction variables. Or, is a case of IV opts not able to coalesce copies of induction variables. A previous post related to this was made in PR41026 which had a type promoted loop index variable copied. I believe t