https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531
--- Comment #11 from Rama Malladi <rvmallad at amazon dot com> ---
(In reply to Wilco from comment #10)
> A 1.1% overall performance gain looks good - is there a significant codesize
> hit from this? If so, are there slightly less aggressive settings that still
> get most of the performance gains but at a lower (acceptable) codesize cost?
> It seems there may be scope to improve the default settings of -O2.
Here is a code size comparison of O2 vs. O2 + inline params for SPEC cpu2017
Int Rate benchmarks. One of the concerns for not modifying the default inline
parameters at -O2 is loss of some function observability due to aggressive
inline optimizations.
Benchmark "-O2" "-O2 + inline size
params" increase
500.perlbench_r 8.5M 11M 1.29
502.gcc_r 51M 56M 1.10
505.mcf_r 102K 106K 1.04
520.omnetpp_r 22M 23M 1.05
523.xalancbmk_r 52M 53M 1.02
525.x264_r 2.5M 2.8M 1.12
531.deepsjeng_r 416K 441K 1.06
541.leela_r 2.6M 2.6M 1.00
548.exchange2_r 115K 115K 1.00
557.xz_r 818K 871K 1.06
999.specrand_ir 24K 24K 1.00
