public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109130] 464.h264ref regressed by 6.5% on a Neoverse-N1 CPU with PGO, LTO, -Ofast and -march=native
Date: Wed, 15 Mar 2023 12:56:29 +0000	[thread overview]
Message-ID: <bug-109130-4-vfbjP0S7v3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109130-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
I can't reproduce that. on a Neoverse-N1 I see between those two commits:

./bench-compare.sh 2fc55f51f99 bad177e8487
A       1457 files
D       0 files
M       0 files
Extracted 'loose/2fc55f51f99:2fc55f51f99'
A       1457 files
D       0 files
M       0 files
Extracted 'loose/bad177e8487:bad177e8487'

difference: 0.083458946886789971215830257097%

Compiled with -Ofast -march=native -g -flto=auto and PGO enabled. as extracted
from
https://lnt.opensuse.org/db_default/v4/SPEC/34263?show_stddev=yes&show_all=yes&show_all_samples=yes&num_comparison_runs=0&test_filter=&test_min_value_filter=&aggregation_fn=min&MW_confidence_lv=0.05&compare_to=34183&baseline=23835&submit=Update

our non PGO runs also didn't see a regression.

  reply	other threads:[~2023-03-15 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 17:03 [Bug target/109130] New: " jamborm at gcc dot gnu.org
2023-03-15 12:56 ` tnfchris at gcc dot gnu.org [this message]
2023-03-20 16:49 ` [Bug target/109130] [13 Regression] " pinskia at gcc dot gnu.org
2023-04-26  6:58 ` [Bug target/109130] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2024-03-08 15:38 ` law at gcc dot gnu.org
2024-05-21  9:14 ` [Bug target/109130] [13/14/15 " jakub 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-109130-4-vfbjP0S7v3@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).