public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fkastl at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113832] New: [14 Regression] 6% exec time regression of 464.h264ref on aarch64
Date: Thu, 08 Feb 2024 15:44:11 +0000	[thread overview]
Message-ID: <bug-113832-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113832
           Summary: [14 Regression] 6% exec time regression of 464.h264ref
                    on aarch64
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: needs-bisection
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fkastl at suse dot cz
  Target Milestone: ---
              Host: aarch64-gnu-linux
            Target: aarch64-gnu-linux

As seen here

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

between commits

g:cc7aebff74d89675
g:314cbfe2980b32f5

there is a 6% slowdown of the 464.h264ref 2006 SPEC benchmark. Compiler options
are:

-Ofast -march=native -flto PGO

The CPU is Ampere Altra - Neoverse N1.

             reply	other threads:[~2024-02-08 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 15:44 fkastl at suse dot cz [this message]
2024-02-08 15:48 ` [Bug target/113832] " pinskia at gcc dot gnu.org
2024-02-08 15:52 ` pinskia at gcc dot gnu.org
2024-02-08 17:28 ` roger at nextmovesoftware dot com
2024-03-07 20:40 ` law at gcc dot gnu.org
2024-03-19 16:18 ` pheeck at gcc dot gnu.org
2024-04-30 13:22 ` [Bug target/113832] [14/15 " pheeck at gcc dot gnu.org
2024-04-30 13:43 ` roger at nextmovesoftware dot com
2024-05-07  7:45 ` rguenth 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-113832-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).