From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 06A613858D37; Wed, 24 Jan 2024 22:41:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 06A613858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706136071; bh=FjGfCtqCN/rw4QGH5ItzYFEW4mfvIcfc88XWFVbWWZk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HDb36V4cbP5XBierEZa6OsDu2XAtUJhRs2I1HzieAGfXlwTYnlqzkxmDOV1ofg6oF Gv4LGye5PaUHARbIbXdaL4XRlak6cHbJPG9UM331aZlwSB9/1Fz8VviXux2ZZA1dkJ qPbDQqNHPAhc7QmETgvkEROa5yUAHYJM0vS4KTH0= From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105275] 525.x264_r and 538.imagick_r regressed on x86_64 at -O2 with PGO after r12-7319-g90d693bdc9d718 Date: Wed, 24 Jan 2024 22:41:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: missed-optimization 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: 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=3D105275 --- Comment #3 from Martin Jambor --- I have re-checked this year again (using master revision r14-7200-g95440171d0e615) but this time on a high-frequency Zen3 CPU (EPYC 75F3). Run-time of 525.x264_r built with master with PGO and -O2 improved by 5.49% compared to GCC 13 and so compared to GCC 11 the regression dropped to 4.2%. Run-time of 538.imagick_r compiled with the same options and master is 5.8% slower on this CPU than when compiling it with GCC 11. With both PGO and LTO, 525.x264_r is now only 2.8% slower than GCC 11. In = case of 538.imagick_r the regression is 2.01% on the zen4, but it is 7.49% on a = zen4 machine :-/=