https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106293
--- Comment #22 from Martin Jambor <jamborm at gcc dot gnu.org> --- (In reply to Jan Hubicka from comment #21) > Fixing loop distribution and vectorizer profile update seems to do the trick > with profile feedback. Without we are still worse than in July last year on > zen2 tester (zen3 and ice lake seems to behave differently perhaps due to > different vectorization decisions) > > https://lnt.opensuse.org/db_default/v4/SPEC/graph?highlight_run=38536&plot. > 0=476.180.0 > > shows two jumps last year. > g:d489ec082ea21410 (2022-06-30 16:46) and 3731dd0bea8994c3 (2022-07-04 00:16) On a machine very similar to lntzen3, hmmer binary built with these two revisions ran for pretty much the same time. > g:3731dd0bea8994c3 (2022-07-04 00:16) and 07dd0f7ba27d1fe9 (2022-07-05 14:05) Bisecting in this range led to g:d2a89866660 but that is the commit referenced in the summary of this bug.
