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 tree-optimization/107499] New: 433.milc regressed by 6-8% on zen3 at -O2 -flto
Date: Tue, 01 Nov 2022 17:27:45 +0000 [thread overview]
Message-ID: <bug-107499-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107499
Bug ID: 107499
Summary: 433.milc regressed by 6-8% on zen3 at -O2 -flto
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: x86_64-linux
Target: x86_64-linux
LNT reports a 8.5% regression of 433.milc when compiled with -O2 -flto
on a zen3 machine:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=469.70.0
On a similar machine I reproduced it as a 6.5% regression and bisected
it to 19295e8607d (tree-optimization/100756 - niter analysis and
folding).
Possibly related, possibly not:
- An intel machine results show something which might be a 2%
regression around the same time at -O2 -flto -march=native.
See https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=790.70.0
- In the same time-frame there is also a 5% performance drop on zen2
with -Ofast -flto -march=native, but those results have been rather
flaky in the past (see PR 101296):
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=289.70.0
- there is a 11% regression reported on the same zen3 machine when
using O2 flto -march=native but either I cannot reproduce it or it
does not seem to be caused by the same commit. I'll wait for more
LNT results before investigating. See
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=465.70.0
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
next reply other threads:[~2022-11-01 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 17:27 jamborm at gcc dot gnu.org [this message]
2022-11-05 10:42 ` [Bug tree-optimization/107499] [13 Regression] " rguenth at gcc dot gnu.org
2022-12-01 10:31 ` marxin at gcc dot gnu.org
2022-12-02 8:36 ` marxin at gcc dot gnu.org
2023-02-01 9:31 ` 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-107499-4@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).