From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C09D83858C39; Mon, 17 Apr 2023 16:15:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C09D83858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681748112; bh=393+b0RFXaoc3bgM4NTwz4RNibq/iFHPEI9/8NxIL6I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LfY4u6EZAQinVycTybtEhrPNmr/l/+34+ENt+okP9wIshPEEX+ItEtca3N0Pcqsjz NWV7mp/8zkM2ASkybUjHAGLao71+AMAlA95JcUT7Vw4k7kofS29hpBrA4/Yz8GXhyj s1Eso3lNFjALd9v92ogwurVanALJ74XyoO1H/+Cc= From: "jamborm 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, 17 Apr 2023 16:15:12 +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.0 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 #12 from Martin Jambor --- My understanding of comment #2 and #3 is that we end up with what are very likely bogus BB counts that we should check and perhaps attempt to fix.=