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/112916] [14 Regression] ~4-7% exec time regression of 433.milc on AMD Zen2
Date: Wed, 13 Dec 2023 09:17:24 +0000	[thread overview]
Message-ID: <bug-112916-4-aFjs2brP0j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112916-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Filip Kastl <fkastl at suse dot cz> ---
Sometimes there are gaps in the data our team gathers, unfortunately. One cause
can be that upstream GCC temporarily fails to build a benchmark. That shouldn't
matter in this case I think. The last gap for this benchmark was in September.

  parent reply	other threads:[~2023-12-13  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08  7:47 [Bug target/112916] New: " fkastl at suse dot cz
2023-12-08  8:24 ` [Bug target/112916] " rguenth at gcc dot gnu.org
2023-12-13  9:17 ` fkastl at suse dot cz [this message]
2024-03-07 20:59 ` law at gcc dot gnu.org
2024-05-07  7:43 ` [Bug target/112916] [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-112916-4-aFjs2brP0j@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).