public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/90151] 554.roms_r regression on x86_64 at -O2 and generic march/mtune
Date: Thu, 20 Jan 2022 16:50:21 +0000	[thread overview]
Message-ID: <bug-90151-4-46OQGYNIiq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90151-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Reconfirmed in 2021 too, also on LNT.  The best way to see current
status is probably to go to
https://lnt.opensuse.org/db_default/v4/SPEC/spec_report/branch?sorting=gcc-7%2Cgcc-8%2Cgcc-9%2Cgcc-10%2Cgcc-11%2Cgcc-trunk
and then enter "554.roms" into the "test name filter" edit field.

On Zen3 we now regress by 5.63% compared to GCC 7 at -O2.

On Zen2 we now regress by 8.35% compared to GCC 7 at -O2.

On Zen1 we now regress by 11.15% compared to GCC 7 at -O2.

On s Kabylake "client" CPU we now regress by 9.06% compared to GCC 7 at -O2.

On a Cascadelake "server" CPU we now regresss by 7.84% compared to GCC 7 at
-O2.

  parent reply	other threads:[~2022-01-20 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90151-4@http.gcc.gnu.org/bugzilla/>
2020-03-30 20:31 ` jamborm at gcc dot gnu.org
2022-01-20 16:50 ` jamborm at gcc dot gnu.org [this message]
2023-01-31  0:02 ` jamborm 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-90151-4-46OQGYNIiq@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).