public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: paul zimmermann <Paul.Zimmermann@inria.fr>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org
Subject: Re: [PATCH 1/5] benchtests: Add exp10f benchmark
Date: Wed, 15 Apr 2020 10:05:57 +0200	[thread overview]
Message-ID: <mwtv1ltbq2.fsf@tomate.loria.fr> (raw)
In-Reply-To: <DB8PR08MB50366E360127AEED241B7F5583DA0@DB8PR08MB5036.eurprd08.prod.outlook.com> (message from Wilco Dijkstra on Tue, 14 Apr 2020 11:15:05 +0000)

       Dear Wilco,

> Also keeping the workload line means we get more accurate benchmark
> results, including throughput and latency.

however, it makes difficult to compare to other functions which don't have
the workload line, for example sinf. Why don't all float functions have the
same workload?

zimmerma@tomate:/localdisk/zimmerma/glibc/benchtests$ grep workload *f-inputsexp2f-inputs:## name: workload-spec2017.wrf
expf-inputs:## name: workload-spec2017.wrf
log2f-inputs:## name: workload-spec2017.wrf
logf-inputs:## name: workload-spec2017.wrf
powf-inputs:## name: workload-spec2006.wrf

Paul

  parent reply	other threads:[~2020-04-15  8:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 11:15 Wilco Dijkstra
2020-04-14 12:18 ` Adhemerval Zanella
2020-04-15  8:05 ` paul zimmermann [this message]
2020-04-15  8:51   ` Wilco Dijkstra
  -- strict thread matches above, loose matches on Subject: below --
2020-06-18 16:17 Wilco Dijkstra
2020-04-09 19:59 Adhemerval Zanella
2020-04-16 20:41 ` Adhemerval Zanella
2020-04-29 17:11   ` Adhemerval Zanella
2020-05-20 20:18     ` Adhemerval Zanella

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=mwtv1ltbq2.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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).