On 24.01.2011 11:23, Christophe Lyon wrote:
> OK, I am going to have a look at gitorious. In the mean time, I have a bit of
> cleanup and minimal documentation to perform.
>
Hi,
You can have a look at http://gitorious.org/arm-neon-tests/arm-neon-tests.
For sure it will need some polishing, but i
>> 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 bi
On Fri, Jan 21, 2011 at 11:25:05PM +, Peter Maydell wrote:
> On 21 January 2011 10:07, Christophe Lyon 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 referen
On 21 January 2011 10:07, Christophe Lyon 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 foll
Hi all,
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
