On Sun, Nov 16, 2014 at 10:08 PM, David Edelsohn <dje....@gmail.com> wrote: > Because they have not shown general performance benefit.
Also they very often cause very long compile-times. > I hope that the renewed attention and development effort will allow > them to be enabled by default eventually. Yeah - though I'd like to have a group flag that enables the mature ones. Mature here means transforms that guard themselves properly for long compile-time and ones that have a cost model (may be a runtime check even). Thanks, Richard. > Thanks, David > > On Sun, Nov 16, 2014 at 2:10 PM, Andi Kleen <a...@firstfloor.org> wrote: >> >> Is there any specific reason why none of the graphite loop optimizations >> (loop-block, loop-interchange, loop-strip-mine, loop-jam) >> are enabled with -O3 or -Ofast? >> >> I assume doing so would make them much more widely used. >> >> Perhaps would be something to consider for 5.0? >> >> -Andi >>
