public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Andras Tantos <andras@tantosonline.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Benchmark recommendations needed
Date: Tue, 15 Feb 2022 15:31:04 +0100	[thread overview]
Message-ID: <CAFiYyc3dAYtBmm+_bxXdTiCSQ0bhSXiXuwLTddehzo5Dm_t_Mw@mail.gmail.com> (raw)
In-Reply-To: <b67726c8ccde7804310883ac1e6fcf07c6c472a2.camel@tantosonline.com>

On Tue, Feb 15, 2022 at 3:25 PM Andras Tantos <andras@tantosonline.com> wrote:
>
> Hello all!
>
> I'm working on porting GCC to a new processor architecture. I think
> I've finally got to a fairly stable stage, so the next logical step
> would be to test and optimize. For that, I would need some benchmarks,
> and this is where I'm seeking your help.
>
> This being a hobby project, I can't shell out $1000+ for the spec
> suite. On top of that, I only have newlib ported as the runtime, which
> means very limited support for OS facilities.
>
> I already have dhrystone, but what else would you recommend using?
>
> I'm looking for 'general purpose' payloads, things, where I can judge
> object code size, instruction set utilization, look for tuning
> opportunities, etc.
>
> I would like to also be able to compare the results with other
> architectures (FPGA cores, such as nios2 as well as some low-end cores,
> such as 32-bit arm/thumb and riscv-RV32IMFC).
>
> So, can you suggest some benchmarks or applications to be used as ones?

There's scimark and nbench and for scientific there's fortran polyhedron.
The botan crypto library also has some extensive benchmark setup
for crypto kernels.

Richard.

> Thanks a bunch!
> Andras
>
>

  reply	other threads:[~2022-02-15 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 22:23 Andras Tantos
2022-02-15 14:31 ` Richard Biener [this message]
2022-02-17 17:15 ` Hans-Peter Nilsson
2022-02-17 18:27 ` andras
     [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
2022-02-23  0:59         ` Patrick McGehearty
2022-02-23 17:01           ` 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=CAFiYyc3dAYtBmm+_bxXdTiCSQ0bhSXiXuwLTddehzo5Dm_t_Mw@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=andras@tantosonline.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).