public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chz0808 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114978] [14/15 regression] 548.exchange2_r 14%-28% regressions on Loongarch64 after gcc 14 snapshot 20240317
Date: Wed, 08 May 2024 14:41:17 +0000 [thread overview]
Message-ID: <bug-114978-4-cTswaMa2Ik@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114978-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #7 from Chen Chen <chz0808 at gmail dot com> ---
(In reply to Richard Biener from comment #6)
> https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=471.407.0
>
> shows a recent improvement that then regressed again, maybe you have a
> similar artifact with the choosing of the snapshots. Try a snapshot from
> february for comparison for example.
Thanks for the nice graph!
We did more tests on AMD Zen4 CPU R9 7940HS (system: Debian 12) and used
similar parameters as yours. The results are following:
with parameters "-m64 -g -Ofast -march=native":
13.2.0: 30.0 (87.2s) [gcc 13.2 release]
20240121: 29.8 (88.0s) [gcc 14 snapshot]
20240218: 29.8 (88.0s) [gcc 14 snapshot]
20240303: 29.2 (89.8s) [gcc 14 snapshot]
20240310: 31.7 (82.6s) [gcc 14 snapshot]
20240317: 31.7 (82.7s) [gcc 14 snapshot]
20240324: 28.3 (92.5s) [gcc 14 snapshot]
20240430: 28.4 (92.3s) [gcc 14 snapshot, 14.1.0-RC]
14.1.0: 28.4 (92.4s) [gcc 14.1 release]
with parameters "-m64 -g -Ofast -march=native -flto":
13.2.0: 30.5 (85.8s) [gcc 13.2 release]
20240121: 30.5 (85.9s) [gcc 14 snapshot]
20240218: 29.5 (88.7s) [gcc 14 snapshot]
20240303: 30.5 (86.0s) [gcc 14 snapshot]
20240310: 31.6 (82.8s) [gcc 14 snapshot]
20240317: 31.7 (82.7s) [gcc 14 snapshot]
20240324: 28.6 (91.6s) [gcc 14 snapshot]
20240430: 29.1 (89.9s) [gcc 14 snapshot, 14.1.0-RC]
14.1.0: 29.1 (90.1s) [gcc 14.1 release]
The scores with gcc 14.1 release are 8.2-10.4% lower than those with gcc 14
snapshot 20240317, and 4.6-5.3% lower than those with gcc 13.2 release.
next prev parent reply other threads:[~2024-05-08 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 17:58 [Bug fortran/114978] New: " chz0808 at gmail dot com
2024-05-07 18:12 ` [Bug fortran/114978] [14/14 regression] " sjames at gcc dot gnu.org
2024-05-07 18:13 ` xry111 at gcc dot gnu.org
2024-05-07 18:17 ` [Bug target/114978] " xry111 at gcc dot gnu.org
2024-05-07 18:18 ` xry111 at gcc dot gnu.org
2024-05-08 1:41 ` [Bug target/114978] [14/15 " chenglulu at loongson dot cn
2024-05-08 8:20 ` rguenth at gcc dot gnu.org
2024-05-08 14:41 ` chz0808 at gmail dot com [this message]
2024-05-09 2:44 ` chenglulu at loongson dot cn
2024-05-09 3:36 ` xry111 at gcc dot gnu.org
2024-05-09 3:40 ` chenglulu at loongson dot cn
2024-05-09 11:09 ` chenglulu at loongson dot cn
2024-05-09 12:57 ` chz0808 at gmail dot com
2024-05-09 13:09 ` xry111 at gcc dot gnu.org
2024-05-10 3:12 ` chz0808 at gmail dot com
2024-05-10 3:15 ` chenglulu at loongson dot cn
2024-05-15 1:24 ` chenglulu at loongson dot cn
2024-05-15 3:41 ` xry111 at gcc dot gnu.org
2024-05-15 3:57 ` chenglulu at loongson dot cn
2024-05-21 12:46 ` chenglulu at loongson dot cn
2024-05-21 12:47 ` chenglulu at loongson dot cn
2024-05-21 13:01 ` xry111 at gcc dot gnu.org
2024-05-21 13:04 ` chenglulu at loongson dot cn
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-114978-4-cTswaMa2Ik@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).