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 middle-end/112697] New: [14 Regression] 30-40% exec time regression of 433.milc on zen2 Date: Fri, 24 Nov 2023 09:03:48 +0000 [thread overview] Message-ID: <bug-112697-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697 Bug ID: 112697 Summary: [14 Regression] 30-40% exec time regression of 433.milc on zen2 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization, needs-bisection Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: fkastl at suse dot cz Target Milestone: --- Host: x86_64-linux Target: x86_64-linux Between commits g:0c305f3dec9a992dd775a3b9607b7b1e8c051859 g:7f974c5fd4f59a9d8dd20c49a0e2909cb290f4b4 there's a 30-40% slowdown of the 433.milc 2006SPEC benchmark as seen here: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=292.70.0 It's 40% here and I also measured the slowdown on another zen2 machine where the difference was 30%. Compile options: -g -O2 -flto=128
next reply other threads:[~2023-11-24 9:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-24 9:03 fkastl at suse dot cz [this message] 2023-11-24 9:07 ` [Bug middle-end/112697] " fkastl at suse dot cz 2023-11-24 9:51 ` rguenth at gcc dot gnu.org 2023-11-24 17:45 ` jamborm at gcc dot gnu.org 2023-11-24 17:52 ` [Bug middle-end/112697] [14 Regression] 30-40% exec time regression of 433.milc on zen2 since r14-4972-g8aa47713701b1f sjames at gcc dot gnu.org 2023-11-27 11:58 ` amonakov at gcc dot gnu.org 2023-11-29 13:52 ` jamborm at gcc dot gnu.org 2023-11-29 13:53 ` jamborm at gcc dot gnu.org 2023-12-01 15:37 ` amonakov at gcc dot gnu.org 2023-12-01 16:00 ` amonakov at gcc dot gnu.org 2024-03-07 21:01 ` law at gcc dot gnu.org 2024-03-21 9:45 ` pheeck at gcc dot gnu.org 2024-03-22 12:47 ` law 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-112697-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).