From: Paul Koning <paulkoning@comcast.net>
To: Gary Oblock <gary@amperecomputing.com>
Cc: Andras Tantos <andras@tantosonline.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Benchmark recommendations needed
Date: Tue, 22 Feb 2022 16:49:06 -0500 [thread overview]
Message-ID: <2216839E-05A8-4FBC-B86A-7C51E5DBCA90@comcast.net> (raw)
In-Reply-To: <BYAPR01MB54641DCB927010838859DD67C63B9@BYAPR01MB5464.prod.exchangelabs.com>
> On Feb 22, 2022, at 4:26 PM, Gary Oblock via Gcc <gcc@gcc.gnu.org> wrote:
>
> Andras,
>
> The whole point of benchmarks is to judge a processor's performance.
> That being said, just crippling GCC is not reasonable because
> processors must be judged in the appropriate context and that
> includes the current state of the art compiler technology. If you have
> a new processor I'd benchmark it using the applications you built it
> for.
Exactly. Part of what you want to see is that GCC optimizes well for the new machine, i.e., that there aren't artifacts of the machine description that get in the way of optimization.
So you'd want to use applications that are good exercises not just of the code generator but also the optimizer. Dhrystone isn't really that, because it has evolved into mostly an optimizer test, not a machine or code generator test.
paul
next prev parent reply other threads:[~2022-02-22 21:49 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
2022-02-22 21:26 ` Gary Oblock
2022-02-22 21:49 ` Paul Koning [this message]
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=2216839E-05A8-4FBC-B86A-7C51E5DBCA90@comcast.net \
--to=paulkoning@comcast.net \
--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).