Re: Reduce inline limits a bit to compensate changes in inlining metrics

2018-02-13 Thread Jan Hubicka
> Hi. > > I see quite SPEC 2006 benchmark changes for -Ofast -march=native: > (note that size changes are not presented all) Thanks! It is interesting that I do not see similar observations on Czerny which also runs spec2006. In partiuclar both AMD machines agrees on soplex milc and bwaves.

Re: Reduce inline limits a bit to compensate changes in inlining metrics

2018-02-13 Thread Martin Liška
Hi. I see quite SPEC 2006 benchmark changes for -Ofast -march=native: (note that size changes are not presented all) 1) gillan (AMD bulldozer): +--+---+--+--+---+---+---+ | Performance Regressions - Execution Time | Δ |

Re: Reduce inline limits a bit to compensate changes in inlining metrics

2018-02-12 Thread Richard Biener
On Fri, 9 Feb 2018, Jan Hubicka wrote: > Hi, > this patch addresses the code size regression by reducing > max-inline-insns-auto 40->30 and increasing inline-min-speedup 8->15. > > The main reason why we need retuning is following > > - inline-min-speedup works in a way that if expected

Reduce inline limits a bit to compensate changes in inlining metrics

2018-02-09 Thread Jan Hubicka
Hi, this patch addresses the code size regression by reducing max-inline-insns-auto 40->30 and increasing inline-min-speedup 8->15. The main reason why we need retuning is following - inline-min-speedup works in a way that if expected runtime of caller+calee combo after inlining reduces by