From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: eCos Developers List <ecos-devel@ecos.sourceware.org>
Subject: whetstone test
Date: Fri, 26 Nov 2010 09:16:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1011261029060.10695@sg-desktop.belvok.com> (raw)
Hi,
What is your opinion, Is it a good idea to have `whetstone' test for
eCos? http://en.wikipedia.org/wiki/Whetstone_(benchmark)
The source can be grabbed from here: http://www.netlib.org/benchmark/ I
use http://www.netlib.org/benchmark/whetstone.c (FYI: no warnings with
nowadays toolchains).
If your answer will be, 'Yes, it is', my next question: where to have
the test? I placed it together with `dhrystone' test under eCos kernel
tests with a minimal tweak for CYGPKG_KERNEL_TESTS CDL option:
. ((CYGPKG_LIBM) ? " tests/whetstone" : "")
Of course, I would place the test together with the libm tests if that
is more suitable place. What is better?
NOTE: Mostly, I use the test to know how evolved the eCos toolchains.
Sergei
next reply other threads:[~2010-11-26 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 9:16 Sergei Gavrikov [this message]
2010-11-26 18:03 ` John Dallaway
2010-11-26 18:17 ` Sergei Gavrikov
2010-11-27 13:11 ` Sergei Gavrikov
2010-11-30 9:50 ` John Dallaway
2010-11-30 11:01 ` Sergei Gavrikov
2010-12-01 18:55 ` Sergei Gavrikov
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=alpine.DEB.2.00.1011261029060.10695@sg-desktop.belvok.com \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.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).