public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109130] New: 464.h264ref regressed by 6.5% on a Neoverse-N1 CPU with PGO, LTO, -Ofast and -march=native
Date: Tue, 14 Mar 2023 17:03:42 +0000	[thread overview]
Message-ID: <bug-109130-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109130
           Summary: 464.h264ref regressed by 6.5% on a Neoverse-N1 CPU
                    with PGO, LTO, -Ofast and -march=native
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamborm at gcc dot gnu.org
                CC: tnfchris at gcc dot gnu.org
            Blocks: 26163
  Target Milestone: ---
              Host: aarch64-suse-linux
            Target: aarch64-suse-linux

LNT shows what looks like a clear recent 6.5% regression on the
464.h264ref benchmark from SPEC 2006 CPU suite when compiled with
PGO, LTO, -Ofast and -march=native on a Neoverse-N1 CPU:

  https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=586.220.0

In the same time period, I cannot (immediately) see any similar
regressions on any other CPU (all others that we monitor are x86_64)
or option combination.

Unfortunately I don't have the time and resources to further
investigate, but the commit range bad177e848787258..2fc55f51f9953b45
includes 8e26ac4749c (AArch64: Fix codegen regressions around tbz),
among other things.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)

             reply	other threads:[~2023-03-14 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 17:03 jamborm at gcc dot gnu.org [this message]
2023-03-15 12:56 ` [Bug target/109130] " tnfchris at gcc dot gnu.org
2023-03-20 16:49 ` [Bug target/109130] [13 Regression] " pinskia at gcc dot gnu.org
2023-04-26  6:58 ` [Bug target/109130] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2024-03-08 15:38 ` law at gcc dot gnu.org
2024-05-21  9:14 ` [Bug target/109130] [13/14/15 " jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109130-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).