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: Thu, 09 May 2024 12:57:16 +0000 [thread overview]
Message-ID: <bug-114978-4-i3zZ4bPRm8@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 #12 from Chen Chen <chz0808 at gmail dot com> ---
(In reply to chenglulu from comment #11)
> (In reply to Chen Chen from comment #0)
> > We tested Loongarch64 CPU Loongson 3A6000 with "LA664" architecture in Linux
> > operating system AOSC OS 11.4.0 (default gcc version is 13.2.0). And we
> > found the 548.exchange2_r benchmark from SPEC 2017 INTrate suite suffered
> > significant regressions from 14% to 28% with various compiling options.
> >
> > The rate-1 results are following:
> >
> > after snapshot 20240317 score 14.3-19.3% lower with parameters "-g -Ofast
> > -march=native":
> > 13.2.0: 11.7 (223s) [gcc 13.2.0, system default]
> Hi：
>
> I can't reproduce the score of r13.2. Have you made any modifications there?
No. I used system default gcc. How big is the difference? A little fluctuation
is normal. I once got scores 11.3(232s)、11.5(227s) with parameters "-g -Ofast
-march=native" in previous tests too. To be fair, in each test presented above
I always free page cache by the command "echo 3 > /proc/sys/vm/drop_caches" and
then run the test.
next prev parent reply other threads:[~2024-05-09 12:57 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
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 [this message]
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-i3zZ4bPRm8@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).