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: Tue, 30 Nov 2010 11:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1011301235490.2074@sg-desktop.belvok.com> (raw)
In-Reply-To: <4CF4C8EF.9010403@dallaway.org.uk>
Hi John,
John Dallaway wrote:
> Hi Sergei
>
> Sergei Gavrikov wrote:
>
> > 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.
>
> IANAL either.
>
> I note that we _do_ have a precedent for including benchmark code with
> no stated copyright and licensing terms. Namely, the dhrystone test:
>
> http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/packages/kernel/current/tests/dhrystone.c?rev=1&content-type=text/x-cvsweb-markup&cvsroot=ecos
Yep, I did take a look on the dhrystone's header in CVS at that moment
and I thought, Why not have the same reservation about whetstone test,
but still...
> In my opinion, including a whetstone test adapted from the original
> whets.c code from http://www.roylongbottom.org.uk/whets.c would be
> acceptable (avoiding other versions with company copyright notices). Do
> any of the other maintainers have an opinion on this?
> I would be inclined to place the test alongside the dhrystone test in
> the kernel package with similar pre-processor tests for correct
> configuration of eCos, similar implementation of dtime() and similar use
> of __ECOS__ to annotate eCos-specific changes. I would also suggest
> #ifdefs allowing the test to build both with and without libm since only
> two of the test sections (N5, N8) appear to require libm.
Thank you for your expert opinion.
If other maintainers would have no objection on the source of the test I
would adapt its source code for eCos environment/needs, test and post a
result patch to eCos Bugzilla registrar.
Thank you,
Sergei
> John Dallaway
> eCos maintainer
next prev parent reply other threads:[~2010-11-30 11:01 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
2010-11-30 9:50 ` John Dallaway
2010-11-30 11:01 ` Sergei Gavrikov [this message]
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.1011301235490.2074@sg-desktop.belvok.com \
--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).