From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Developers List <ecos-devel@ecos.sourceware.org>
Subject: Re: whetstone test
Date: Sat, 27 Nov 2010 13:11:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1011271436190.31773@sg-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1011262011540.20343@sg-laptop>
On Fri, 26 Nov 2010, Sergei Gavrikov wrote:
> On Fri, 26 Nov 2010, John Dallaway wrote:
> > Sergei Gavrikov wrote:
> >
> > > What is your opinion, Is it a good idea to have `whetstone' test for
> > > eCos? http://en.wikipedia.org/wiki/Whetstone_(benchmark)
> >
> > What is the license and copyright situation with this benchmark code?
> > The source code at:
> >
> > http://freespace.virgin.net/roy.longbottom/whets.c
> >
> > does not include this information.
>
> I confess that I have not thought about it :-( Here are just now checked
> out where it can be (my version) http://en.wikipedia.org/wiki/Netlib
> My mistake. I will look around other implementations.
Hi John,
I found a remake of whetstone.c test (original one came from UNIX world
as I could understand) on one NetBSD FTP mirror. I would not want to
paste URL address now, but it leaves under 'NetBSD/packages/distfiles'
directory. Can it be "a pass"? Also there is another test 'flops.c' (it
calculates the MFLOPS value) in the NetBSD packages.
Both of NetBSD sources can be dig with a 'FileWatcher' Search Engine:
http://www.filewatcher.com
Can you, please, check copyright header for that whetstone.c (1.2) from
NetBSD packages?
IANAL and I would withdraw my questions if NetBSD trunk is not (C)-pass.
Thank you,
Sergei
next prev parent reply other threads:[~2010-11-27 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 9:16 Sergei Gavrikov
2010-11-26 18:03 ` John Dallaway
2010-11-26 18:17 ` Sergei Gavrikov
2010-11-27 13:11 ` Sergei Gavrikov [this message]
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.1011271436190.31773@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).