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/113832] [14 Regression] 6% exec time regression of 464.h264ref on aarch64 Date: Tue, 19 Mar 2024 16:18:14 +0000 [thread overview] Message-ID: <bug-113832-4-0RrC5gkfU7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113832 --- Comment #3 from Filip Kastl <pheeck at gcc dot gnu.org> --- It seems that the benchmark runtime returned to normal for a while but then went back to 6% slowdown. Somewhere between these two commits the benchmark sped up g:eb7a8f213d59e0cf g:15d1dae0d4d1be88 And between these two commits the benchmark regressed once again g:c7a9883663a88861 g:84fc8f4f3263d665
next prev parent reply other threads:[~2024-03-19 16:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-08 15:44 [Bug target/113832] New: " fkastl at suse dot cz 2024-02-08 15:48 ` [Bug target/113832] " pinskia at gcc dot gnu.org 2024-02-08 15:52 ` pinskia at gcc dot gnu.org 2024-02-08 17:28 ` roger at nextmovesoftware dot com 2024-03-07 20:40 ` law at gcc dot gnu.org 2024-03-19 16:18 ` pheeck at gcc dot gnu.org [this message] 2024-04-30 13:22 ` [Bug target/113832] [14/15 " pheeck at gcc dot gnu.org 2024-04-30 13:43 ` roger at nextmovesoftware dot com 2024-05-07 7:45 ` 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-113832-4-0RrC5gkfU7@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).