From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9A1C7385841D; Mon, 31 Jul 2023 15:39:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A1C7385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690817993;
	bh=OIHnJ3BPe1hBCzFTMXXMLOuNCwYDCe+aMG1t9PMqo+0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DODaY9vEAIAST3c3/t1MimgygqsVo7tUeMJVEzGHk07S2ec7Sskt7F3zu5XRTljor
	 dqwS9QK3mWHI43upSut5B9qSwk7v1A75hhHGl4NV+xAOMcC97Yu2AwXQY/bJ6cDCM4
	 5bYi8zeaICvvIVe68IdM2HhHFRxdaL+fX2ku5cLw=
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.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 15:39:51 +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: jamborm 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: <bug-106293-4-GiEw6H4WtW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106293-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106293-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106293

--- 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 tr=
ick
> 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)
>=20
> https://lnt.opensuse.org/db_default/v4/SPEC/graph?highlight_run=3D38536&p=
lot.
> 0=3D476.180.0
>=20
> 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.=