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 tree-optimization/114268] New: [14 Regression] 5% exec time regression in 454.calculix on Aarch64
Date: Thu, 07 Mar 2024 14:41:17 +0000	[thread overview]
Message-ID: <bug-114268-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114268
           Summary: [14 Regression] 5% exec time regression in
                    454.calculix on Aarch64
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: missed-optimization, needs-bisection
          Severity: normal
          Priority: P3
         Component: tree-optimization
          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 on the graph here

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

between

g:e42287eaed2c93f1
and
g:4d9da4199d1cc067

we detected a 5% exec time slowdown of the 454.calculix 2006 SPEC benchmark
with the cmdline options -O2 -march=native -flto on our aarch64 machine (ampere
altra).


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:[~2024-03-07 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 14:41 pheeck at gcc dot gnu.org [this message]
2024-03-08  8:16 ` [Bug tree-optimization/114268] " rguenth at gcc dot gnu.org
2024-03-10  4:18 ` law at gcc dot gnu.org
2024-03-21  9:22 ` pheeck 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-114268-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).