https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531
--- Comment #13 from Rama Malladi <rvmallad at amazon dot com> --- (In reply to Jan Hubicka from comment #12) > If this is without LTO, can you also try the LTO numbers? > Inliner behaves sifniciantly different with and without LTO, since LTO > introduces many (and often too many) inlining oppurtunities, which > sometimes makes things to out of hand. > > Overal SPEC2k17 without LTO is not the most representative inlining > benchmark, since most programs there are relatively old and written with > small abstraction penalty. The numbers listed above in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531#c11 are with LTO. Here are the base flags used for these runs: `O2 -march=armv8-a+crc+crypto -mtune=native -flto` + inlining params: `--param=early-inlining-insns=14 --param=inline-heuristics-hint-percent=600 --param=inline-min-speedup=15 --param=max-inline-insns-auto=30 --param=max-inline-insns-single=200`
