public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d_vampile at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110059] When SPEC is used to test the GCC (10.3.1), the test result of subitem 548 fluctuates abnormally.
Date: Wed, 31 May 2023 12:14:58 +0000 [thread overview]
Message-ID: <bug-110059-4-Yj2AsqbtM7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110059-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110059
d_vampile <d_vampile at 163 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|10.3.1 |10.3.0
Target| |aarch64
URL| |https://gcc.gnu.org/piperma
| |il/gcc-patches/2019-Septemb
| |er/530304.html
--- Comment #1 from d_vampile <d_vampile at 163 dot com> ---
When the SPEC is used to test the GCC (10.3.0) performance, the test result of
subitem 548 fluctuates abnormally.
Trace the cause of the exception. I analyze that the commit(r276140) is faulty.
Revert this commit(r276140), and the fluctuation of spec 548 test results for
gcc 10.3.0 is significantly reduced. The following is the test result.
GCC 10.3.0 test result:
Benchmarks copies runtime ratio
548.exchange2_r 128 553 607
548.exchange2_r 128 512 654
548.exchange2_r 128 513 654
548.exchange2_r 128 553 607
548.exchange2_r 128 553 607
548.exchange2_r 128 514 652
548.exchange2_r 128 515 652
548.exchange2_r 128 553 607
548.exchange2_r 128 553 607
548.exchange2_r 128 508 660
Test result after revert this commit:
Benchmarks copies runtime ratio
548.exchange2_r 128 520 645
548.exchange2_r 128 680 494
548.exchange2_r 128 527 637
548.exchange2_r 128 679 494
548.exchange2_r 128 524 640
548.exchange2_r 128 679 494
548.exchange2_r 128 524 640
548.exchange2_r 128 524 640
548.exchange2_r 128 520 645
548.exchange2_r 128 521 644
next prev parent reply other threads:[~2023-05-31 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:43 [Bug target/110059] New: " d_vampile at 163 dot com
2023-05-31 12:14 ` d_vampile at 163 dot com [this message]
2023-05-31 12:23 ` [Bug target/110059] " pinskia at gcc dot gnu.org
2023-05-31 13:42 ` ktkachov at gcc dot gnu.org
2023-05-31 13:54 ` jakub at gcc dot gnu.org
2023-06-02 7:30 ` rguenth at gcc dot gnu.org
2023-06-05 1:41 ` d_vampile at 163 dot com
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-110059-4-Yj2AsqbtM7@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).