public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114860] New: [aarch64] 511.povray regresses by ~5.5% with -O3 -flto -march=native -mcpu=neoverse-v2 Date: Fri, 26 Apr 2024 06:25:15 +0000 [thread overview] Message-ID: <bug-114860-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114860 Bug ID: 114860 Summary: [aarch64] 511.povray regresses by ~5.5% with -O3 -flto -march=native -mcpu=neoverse-v2 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: prathamesh3492 at gcc dot gnu.org Target Milestone: --- Hi, It seems performance of povray bmk is regressing ~5.5% with -O3 -flto -march=native -mcpu=neoverse-v2, and ~1.6% without LTO. This seems to have happened after following commit: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=a2f4be3dae04fa8606d1cc8451f0b9d450f7e6e6 Reverting it brings back performance. I am investigating further. Thanks, Prathamesh
next reply other threads:[~2024-04-26 6:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-26 6:25 prathamesh3492 at gcc dot gnu.org [this message] 2024-04-26 14:27 ` [Bug target/114860] [14/15 regression] [aarch64] 511.povray regresses by ~5.5% with -O3 -flto -march=native -mcpu=neoverse-v2 since r14-10014-ga2f4be3dae04fa rguenth at gcc dot gnu.org 2024-04-26 14:30 ` tnfchris at gcc dot gnu.org 2024-04-26 14:46 ` tnfchris at gcc dot gnu.org 2024-05-01 6:22 ` tnfchris at gcc dot gnu.org 2024-05-03 10:45 ` prathamesh3492 at gcc dot gnu.org 2024-05-03 21:20 ` pinskia at gcc dot gnu.org 2024-05-07 7:45 ` rguenth at gcc dot gnu.org 2024-05-16 17:17 ` tnfchris at gcc dot gnu.org 2024-05-22 11:27 ` prathamesh3492 at gcc dot gnu.org 2024-05-22 11:36 ` tnfchris 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-114860-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: linkBe 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).