From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Andras Tantos <andras@tantosonline.com>,
Gary Oblock <gary@amperecomputing.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Benchmark recommendations needed
Date: Tue, 22 Feb 2022 11:42:32 +0000 [thread overview]
Message-ID: <fd74651f-310a-5610-c5b9-67bb4372499d@foss.arm.com> (raw)
In-Reply-To: <33a21357ddb10b187935cf4ea269bb5a7a800c1d.camel@tantosonline.com>
Dhrystone is (and probably always was) a bogus benchmark. It's a
well-known truism that MIPS stands for Meaningless Indication of
Processor Speed, and dhrystone scores are equally meaningless.
Dhrystone fell out of common usage over 20 years ago.
It's not GCC that is being peculiar, it's just Dhrystone is pointless.
R.
On 22/02/2022 05:22, Andras Tantos wrote:
> That's true, I did notice GCC being rather ... peculiar about
> drhystone. Is there a way to make it less clever about the benchmark?
>
> Or is there some alteration to the benchmark I can make to not trigger
> the special behavior in GCC?
>
> Andras
>
> On Mon, 2022-02-21 at 03:19 +0000, Gary Oblock via Gcc wrote:
>> Trying to use the dhrystone isn't going to be very useful. It has
>> many downsides not the least is that gcc's optimizer can run rings
>> about it.
>>
>> Gary
>>
>> ________________________________
>> From: Gcc <gcc-bounces+gary=amperecomputing.com@gcc.gnu.org> on
>> behalf of gcc-request@gcc.gnu.org <gcc-request@gcc.gnu.org>
>> Sent: Tuesday, February 15, 2022 6:25 AM
>> To: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
>> Subject: Re:
>>
>> [EXTERNAL EMAIL NOTICE: This email originated from an external
>> sender. Please be mindful of safe email handling and proprietary
>> information protection practices.]
>>
>>
>> Send Gcc mailing list submissions to
>> gcc@gcc.gnu.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://gcc.gnu.org/mailman/listinfo/gcc
>> or, via email, send a message with subject or body 'help' to
>> gcc-request@gcc.gnu.org
>>
>> You can reach the person managing the list at
>> gcc-owner@gcc.gnu.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Gcc digest..."
>
next prev parent reply other threads:[~2022-02-22 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7085.1644935119.2100866.gcc@gcc.gnu.org>
2022-02-21 3:19 ` Gary Oblock
2022-02-22 5:22 ` Andras Tantos
2022-02-22 11:42 ` Richard Earnshaw [this message]
2022-02-22 21:26 ` Gary Oblock
2022-02-22 21:49 ` Paul Koning
2022-02-23 0:59 ` Patrick McGehearty
2022-02-23 17:01 ` andras
2022-02-14 22:23 Andras Tantos
2022-02-15 14:31 ` Richard Biener
2022-02-17 17:15 ` Hans-Peter Nilsson
2022-02-17 18:27 ` andras
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=fd74651f-310a-5610-c5b9-67bb4372499d@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=andras@tantosonline.com \
--cc=gary@amperecomputing.com \
--cc=gcc@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).