From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8B3063858C2F; Mon, 31 Jul 2023 07:44:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8B3063858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1690789483; bh=U64XcrtNCcrD1vf0ZJBLKgpFPS8ZzF5two6ihe8JSs0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=POwnBLkfZXUlfHrss6SJVSw1RU6Xsun0me8xZfODkMGGOiP/jNJbvqYrFnqgTuQfE sBDiGMN1Cc5XELoCNxtdJtpYzPxxNVTo7WGoUuQQuLF8JBdXc7wXvpsE8AhAuKZRn9 mJaCVj3V4fGqfgnvJtMT0PrcLaLnTaSbnbSQChuM= From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106293] [13/14 Regression] 456.hmmer at -Ofast -march=native regressed by 19% on zen2 and zen3 in July 2022 Date: Mon, 31 Jul 2023 07:44:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106293 --- Comment #21 from Jan Hubicka --- 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=3D38536&plo= t.0=3D476.180.0 shows two jumps last year. g:d489ec082ea21410 (2022-06-30 16:46) and 3731dd0bea8994c3 (2022-07-04 00:1= 6) g:3731dd0bea8994c3 (2022-07-04 00:16) and 07dd0f7ba27d1fe9 (2022-07-05 14:0= 5) Which seems both different from the patch listed (which is even older). Optically it seems that second jump is gone, but it is hard to tell a year later. Martin, it would be great to bisect these two.=