[Bug ipa/94360] 6% run-time regression of 502.gcc_r against GCC 9 when compiled with -O2 and both PGO and LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94360 --- Comment #5 from Martin Jambor --- Well, if the current behavior is a good one (I have not looked at how size/performance trade-off works out) then I am also fine declaring this bug invalid.
[Bug ipa/94360] 6% run-time regression of 502.gcc_r against GCC 9 when compiled with -O2 and both PGO and LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94360 Jan Hubicka changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2023-01-18 Ever confirmed|0 |1 --- Comment #4 from Jan Hubicka --- With -O2 -fprofile-use we now use -O2 inliner limits while previously we switched to effectively -O3 inlining. In a way it makes sense to have -O2 -fprofile-use to produce smaller and bit slower code than -O3 -fprofile-use but it seems that current limits are way too low. I.e. the code size savings does not seem to justify the performance loss. >From maintenance perspective it kind of sucks to have 3 sets of values (-O2, -O3 and -O2 + -fprofile-use) but maybe we can get cheaply out by simply making "known hot" hint to be taken seriously with FDO. FDO inlining is kind of easy since hot calls are known well. I will take a look.
[Bug ipa/94360] 6% run-time regression of 502.gcc_r against GCC 9 when compiled with -O2 and both PGO and LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94360 --- Comment #3 from Martin Jambor --- LNT can still see this, on the zen2 and zen3 machine at least: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=700.337.0=711.337.0=740.337.0=694.337.0; https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=690.337.0=745.337.0=777.337.0=687.337.0; (gcc 9 is the dot in the left bottom corner).
[Bug ipa/94360] 6% run-time regression of 502.gcc_r against GCC 9 when compiled with -O2 and both PGO and LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94360 --- Comment #2 from Martin Jambor --- PR94410 is another O2 PGO+LTO bug where g:2925cad2151 caused a slowdown.
[Bug ipa/94360] 6% run-time regression of 502.gcc_r against GCC 9 when compiled with -O2 and both PGO and LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94360 --- Comment #1 from Martin Liška --- Unfortunately, the mentioned configuration is not tested on LNT periodic benchmarks.
