All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] [RFC] ARM test generator
Date: Tue, 8 Jul 2008 14:26:43 +0100	[thread overview]
Message-ID: <200807081426.43774.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0807080535h4dadd1eev8c076bfb86f72e92@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Tuesday 08 July 2008, Laurent Desnogues wrote:
> Hello,
>
> this is a very simple test generator for ARM.
>
> The aim is to help test instruction correctness since several people
> already noticed some problems, that are not always easy to
> reproduce in the absence of test infrastructure (a big word for such
> a simple thing).

I suggest creating a separate project for this.

I'm unconvinced how much value this actually adds unless you can get fairly 
extensive coverage.  i.e. the interesting bit is how you generate 
test-arm.txt and test-ref.txt. You should also cover different combinations 
of overlapping source/destination operands.

I wrote reasonably extensive self-checking tests for a subset of NEON. However 
it ended up a bit of a mess, needs rewriting (probably in something other 
than C), doesn't cover some of the hard instructions, and the input generator 
needs a lot of improvement.  I've attached it for reference.

GCC also has a set of tests for the NEON compiler intrinsics.  We've 
considered augmenting those to be runtime tests.

Paul

[-- Attachment #2: test-neon.tar.bz2 --]
[-- Type: application/x-tbz, Size: 8399 bytes --]

  reply	other threads:[~2008-07-08 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 12:35 [Qemu-devel] [RFC] ARM test generator Laurent Desnogues
2008-07-08 13:26 ` Paul Brook [this message]
2008-07-08 14:52   ` Laurent Desnogues
2008-07-08 15:28     ` Paul Brook
2008-07-08 15:48       ` Laurent Desnogues

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=200807081426.43774.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=laurent.desnogues@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.