From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christophe Lyon <christophe.lyon@st.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ARM] Contributing tests for Neon
Date: Sat, 22 Jan 2011 15:24:49 +0100 [thread overview]
Message-ID: <20110122142449.GD21090@laped.lan> (raw)
In-Reply-To: <AANLkTinYeHhqMPDDR=DoY4KNthYVdjC290jQ=R14oqhK@mail.gmail.com>
On Fri, Jan 21, 2011 at 11:25:05PM +0000, Peter Maydell wrote:
> On 21 January 2011 10:07, Christophe Lyon <christophe.lyon@st.com> wrote:
> > I have developed some tests for ARM-Neon in the form of C sources files
> > calling ARM Neon intrinsics, and comparing the results of the resulting
> > program with a known reference (eg execution on actual CPU) shows
> > if the execution engine is follows the spec.
> >
> > These tests currently represent 750KB of sources (150 files, 12000 lines),
>
> That's a larger and more comprehensive test suite than I was
> expecting :-) (which is fantastic)
>
> > I have a few questions on how to proceed:
> > - we wish to release the files under the MIT license, is it OK to deliver
> > them as-is in the 'tests' qemu subdir?
> > - given the size of the whole stuff, I don't think it's suitable that I
> > send it on the list for review, what should I do?
>
> How about you make it available somewhere (tarball via http, git
> repository on gitorious, or other method of your choice) for the
> moment? Then we can take a look at it and proceed from there.
I agree, this is a good first step. If possible, its good if you
can publish source and binaries so people with the appropriate
tools can rebuild the tests. Also, when possible, binaries with
debug info can be helpful when analyzing test failures.
Cheers
next prev parent reply other threads:[~2011-01-22 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:07 [Qemu-devel] [ARM] Contributing tests for Neon Christophe Lyon
2011-01-21 23:25 ` Peter Maydell
2011-01-22 14:24 ` Edgar E. Iglesias [this message]
2011-01-24 10:23 ` Christophe Lyon
2011-01-24 17:04 ` Christophe Lyon
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=20110122142449.GD21090@laped.lan \
--to=edgar.iglesias@gmail.com \
--cc=christophe.lyon@st.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).