On Wed, Aug 19, 2009 at 2:07 PM, Richard Guenther<richard.guent...@gmail.com> wrote: > 2009/8/19 Albert Cohen <albert.co...@inria.fr>: >> When debugging graphite, we ran into code bloat issues due to >> pass_complete_unrolli being called very early in the non-ipa >> optimization sequence. Much later, the full-blown pass_complete_unroll >> is scheduled, and this one does not do any harm. >> >> Strangely, this early unrolling pass (tuned to only unroll inner loops) >> is only enabled at -O3, independently of the -funroll-loops flag.
Note it is also enabled at -O2 independently of -funroll-loops just with the restriction to the heuristics that it may not increase code size. This is consistent with the other unroll pass (which even runs unconditionally!). Richard.