From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E5E9E3858436; Thu, 2 Sep 2021 15:38:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E5E9E3858436 From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102178] New: SPECFP 2006 470.lbm regressions on AMD Zen CPUs after r12-897-gde56f95afaaa22 Date: Thu, 02 Sep 2021 15:38:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter blocked target_milestone cf_gcchost cf_gcctarget Message-ID: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2021 15:38:08 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102178 Bug ID: 102178 Summary: SPECFP 2006 470.lbm regressions on AMD Zen CPUs after r12-897-gde56f95afaaa22 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org Blocks: 26163 Target Milestone: --- Host: x86_64-linix Target: x86_64-linux LNT has detected an 18% regression of SPECFP 2006 benchmark 470.lbm when it is compiled with -Ofast -march=3Dnative on a Zen2 machine: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=3D421.240.0&plot.1= =3D301.240.0& ...and similarly a 6% regression when it is run on the same machine with -Ofast: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=3D450.240.0&plot.1= =3D24.240.0& I have bisected both on another zen2 machine to commit r12-897-gde56f95afaaa22 (Run pass_sink_code once more before store_merging). Zen1 machine has also seen a similar -march=3Dnative regression in the same time frame: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=3D450.240.0&plot.1= =3D24.240.0& Zen1 -march=3Dgeneric seems to be unaffected, which is also the case for the Intel machines we track. Although lbm has been known to have weird regressions caused entirely by code layout where the compiler was not really at fault, the fact that both generic code-gen and Zen1 are affected seems to indicate this is not the case. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D26163 [Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95= )=