From: Gary Oblock <gary@amperecomputing.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Benchmark recommendations needed
Date: Mon, 21 Feb 2022 03:19:07 +0000 [thread overview]
Message-ID: <BYAPR01MB546473AB3DC42BE4CDD82C4DC63A9@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <mailman.7085.1644935119.2100866.gcc@gcc.gnu.org>
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 parent reply other threads:[~2022-02-21 3:19 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 [this message]
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
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=BYAPR01MB546473AB3DC42BE4CDD82C4DC63A9@BYAPR01MB5464.prod.exchangelabs.com \
--to=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).