From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org, "H . J . Lu" <hjl.tools@gmail.com>
Subject: [PATCH 1/5] benchtests: Add workload name for cosf
Date: Tue, 31 May 2022 18:34:58 -0300 [thread overview]
Message-ID: <20220531213502.227895-2-adhemerval.zanella@linaro.org> (raw)
In-Reply-To: <20220531213502.227895-1-adhemerval.zanella@linaro.org>
So it can show both reciprocal-throughput and latency.
---
benchtests/cosf-inputs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/benchtests/cosf-inputs b/benchtests/cosf-inputs
index 73d6991cbc..6fba27833a 100644
--- a/benchtests/cosf-inputs
+++ b/benchtests/cosf-inputs
@@ -1,7 +1,7 @@
## args: float
## ret: float
## includes: math.h
-
+## name: workload-random
-0x1.d24c56p-1
-0x1.50ab58p-1
0x1.112339p-6
--
2.34.1
next prev parent reply other threads:[~2022-05-31 21:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 21:34 [PATCH 0/5] Use generic sinf, cosf, and sincosf for i686 Adhemerval Zanella
2022-05-31 21:34 ` Adhemerval Zanella [this message]
2022-05-31 21:47 ` [PATCH 1/5] benchtests: Add workload name for cosf H.J. Lu
2022-05-31 21:34 ` [PATCH 2/5] i686: Use generic cosf implementation for SSE2 version Adhemerval Zanella
2022-05-31 21:46 ` H.J. Lu
2022-05-31 21:35 ` [PATCH 3/5] i686: Use generic sinf " Adhemerval Zanella
2022-05-31 21:47 ` H.J. Lu
2022-05-31 21:35 ` [PATCH 4/5] benchtests: Add workload name for sincosf Adhemerval Zanella
2022-05-31 21:48 ` H.J. Lu
2022-05-31 21:35 ` [PATCH 5/5] math: Use generic sinf implementation for SSE2 version Adhemerval Zanella
2022-05-31 21:51 ` H.J. Lu
2022-06-01 12:42 ` Adhemerval Zanella
2022-06-01 15:14 ` H.J. Lu
2022-06-01 16:06 ` Adhemerval Zanella
2022-05-31 21:48 ` [PATCH 0/5] Use generic sinf, cosf, and sincosf for i686 Noah Goldstein
2022-05-31 21:49 ` H.J. Lu
2022-05-31 21:53 ` Noah Goldstein
2022-06-01 12:36 ` Adhemerval Zanella
2022-06-01 13:12 ` 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=20220531213502.227895-2-adhemerval.zanella@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=hjl.tools@gmail.com \
--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).