public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114481] New: [14 Regression] 14% exec time slowdown of 433.milc on aarch64
Date: Tue, 26 Mar 2024 11:59:59 +0000 [thread overview]
Message-ID: <bug-114481-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114481
Bug ID: 114481
Summary: [14 Regression] 14% exec time slowdown of 433.milc on
aarch64
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization, needs-bisection
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: pheeck at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: aarch64-gnu-linux
Target: aarch64-gnu-linux
As seen here
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=686.70.0
between the commits
g:8b483cd5521de79c
g:81ee1298b47d3f3b
there was an 14% runtime slowdown of 433.milc on aarch64. The CPU is Ampere
Altra Neoverse N1. The compilation options were -O2 -flto PGO.
---
Btw here is a plot that also includes GCC13 and GCC12.
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=686.70.0&plot.4=749.70.0&plot.5=869.70.0
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)
next reply other threads:[~2024-03-26 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 11:59 pheeck at gcc dot gnu.org [this message]
2024-03-26 12:00 ` [Bug target/114481] " pheeck at gcc dot gnu.org
2024-03-27 8:37 ` rguenth at gcc dot gnu.org
2024-03-28 10:31 ` [Bug target/114481] " pheeck at gcc dot gnu.org
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-114481-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).