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/113116] New: ~11-17% exec time regression of 436.cactusADM on aarch64 Date: Fri, 22 Dec 2023 15:21:56 +0000 [thread overview] Message-ID: <bug-113116-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113116 Bug ID: 113116 Summary: ~11-17% exec time regression of 436.cactusADM 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: fkastl at suse dot cz Target Milestone: --- Host: aarch64-linux-gnu Target: aarch64-linux-gnu As seen on the graphs here https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=578.100.0 https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=586.100.0 between commits g:8e0568d8ac9dbfc8 g:5641787abeea0fdc there is a slowdown of 436.cactusADM SPEC2006 benchmark, 11% for Ofast native LTO PGO and 17% for Ofast native LTO. This is on aarch64. I haven't seen similar slowdowns on other architectures.
next reply other threads:[~2023-12-22 15:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-22 15:21 fkastl at suse dot cz [this message] 2023-12-22 15:23 ` [Bug target/113116] " fkastl at suse dot cz 2024-01-03 11:21 ` [Bug target/113116] [14 Regression] " tnfchris at gcc dot gnu.org 2024-01-03 11:30 ` fkastl at suse dot cz 2024-01-06 6:15 ` pinskia at gcc dot gnu.org 2024-03-07 20:53 ` law at gcc dot gnu.org 2024-05-07 7:43 ` [Bug target/113116] [14/15 " 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-113116-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).