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/112548] [14 regression] 5% exec time regression in 429.mcf on AMD zen4 CPU (since r14-5076-g01c18f58d37865) Date: Fri, 15 Mar 2024 10:34:49 +0000 [thread overview] Message-ID: <bug-112548-4-LUGDFbQkjg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112548-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112548 --- Comment #28 from Filip Kastl <pheeck at gcc dot gnu.org> --- Created attachment 57710 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57710&action=edit gcda data for himeno I've tried sharing non-SPEC gcda data between machines. I used this benchmark https://raw.githubusercontent.com/kowsalyaChidambaram/Himeno-Benchmark/master/himenobmtxpa.c I generated the gcda data on a zen4 machine gcc.sh himenobmtxpa.c -std=c99 -Ofast -march=znver4 -mtune=znver4 -g -fprofile-generate and used them on another machine gcc.sh himenobmtxpa.c -std=c99 -Ofast -march=znver4 -mtune=znver4 -g -fprofile-use and everything went fine.
next prev parent reply other threads:[~2024-03-15 10:34 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-15 15:07 [Bug target/112548] New: 5% exec time regression in 429.mcf on AMD zen4 CPU fkastl at suse dot cz 2023-11-16 7:27 ` [Bug target/112548] " rguenth at gcc dot gnu.org 2024-02-13 13:38 ` [Bug target/112548] [14 regression] 5% exec time regression in 429.mcf on AMD zen4 CPU (since r14-5076-g01c18f58d37865) pheeck at gcc dot gnu.org 2024-02-13 13:44 ` pheeck at gcc dot gnu.org 2024-02-13 13:48 ` rdapp at gcc dot gnu.org 2024-02-13 14:48 ` pheeck at gcc dot gnu.org 2024-03-04 13:02 ` rguenth at gcc dot gnu.org 2024-03-04 13:35 ` rdapp at gcc dot gnu.org 2024-03-07 21:01 ` law at gcc dot gnu.org 2024-03-08 14:42 ` rdapp at gcc dot gnu.org 2024-03-12 13:03 ` pheeck at gcc dot gnu.org 2024-03-12 15:05 ` sjames at gcc dot gnu.org 2024-03-13 9:55 ` rdapp at gcc dot gnu.org 2024-03-14 15:24 ` pheeck at gcc dot gnu.org 2024-03-14 15:25 ` pheeck at gcc dot gnu.org 2024-03-14 15:31 ` pheeck at gcc dot gnu.org 2024-03-14 15:57 ` pheeck at gcc dot gnu.org 2024-03-14 15:58 ` pheeck at gcc dot gnu.org 2024-03-14 16:16 ` rdapp at gcc dot gnu.org 2024-03-14 16:28 ` pheeck at gcc dot gnu.org 2024-03-14 16:32 ` rdapp at gcc dot gnu.org 2024-03-14 16:41 ` pheeck at gcc dot gnu.org 2024-03-14 16:43 ` rdapp at gcc dot gnu.org 2024-03-14 17:01 ` pheeck at gcc dot gnu.org 2024-03-14 17:17 ` rdapp at gcc dot gnu.org 2024-03-14 17:32 ` pheeck at gcc dot gnu.org 2024-03-14 21:08 ` rdapp at gcc dot gnu.org 2024-03-14 23:02 ` law at gcc dot gnu.org 2024-03-15 9:00 ` pheeck at gcc dot gnu.org 2024-03-15 9:49 ` rdapp at gcc dot gnu.org 2024-03-15 10:34 ` pheeck at gcc dot gnu.org [this message] 2024-03-15 11:02 ` rdapp at gcc dot gnu.org 2024-05-07 7:42 ` [Bug target/112548] [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-112548-4-LUGDFbQkjg@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).