From: Nathan Froyd <froydnj@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/8] ARM: Fix decoding of VFP forms of VCVT between float and int/fixed
Date: Mon, 6 Dec 2010 11:57:22 -0500 [thread overview]
Message-ID: <20101206165721.GF25904@nightcrawler> (raw)
In-Reply-To: <AANLkTi=Ay6S=Y_6-BHgO309To6KyTO7OT10-j=09i_fw@mail.gmail.com>
On Mon, Dec 06, 2010 at 04:48:25PM +0000, Peter Maydell wrote:
> I'm not sure how well it would fit into being committed to qemu (yet):
> it works as a program where you run half of it on real ARM hardware
> and the other half under qemu (or valgrind) and it compares register
> results after executing instructions by looking at the sigcontext struct
> in a signal handler. Plus there's a perl script to generate random
> instruction set sequences to feed the test program. It could be made
> more automated and independent of having a reference bit of hardware
> but I haven't got round to that yet. (Also since it has utility outside of
> just testing qemu I'm not sure if it really belongs in the qemu repo.)
That does sound a little heavyweight. Scripting gdb is also a possibility.
FWIW--and this is not particularly conducive to random insn
sequences--the approach taken when doing the AltiVec bits was to have
code that looked like:
for each insn:
for a suitable set of inputs:
setup interesting registers (status control registers etc.)
load inputs into registers
execute
record interesting post conditions in file.out
You'd get an output file from real hardware and an output file from the
simulator and then compare them, fixing differences as you go. The
actual code included bits to compare the files as well as doing the
generation.
The output files can be somewhat large, but I'm sure clever engineering
could be applied to make them smaller.
Of course, the *real* problems are in undefined-behavior land. :)
-Nathan
next prev parent reply other threads:[~2010-12-06 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 18:23 [Qemu-devel] [PATCH 0/8] ARM: fix VCVT instructions Peter Maydell
2010-11-11 18:23 ` [Qemu-devel] [PATCH 1/8] ARM: Fix decoding of VFP forms of VCVT between float and int/fixed Peter Maydell
2010-12-06 16:30 ` Nathan Froyd
2010-12-06 16:48 ` Peter Maydell
2010-12-06 16:57 ` Nathan Froyd [this message]
2010-12-06 17:07 ` Peter Maydell
2010-12-08 12:00 ` Peter Maydell
2010-11-11 18:23 ` [Qemu-devel] [PATCH 2/8] ARM: Fix decoding of Neon forms of VCVT between float and fixed point Peter Maydell
2010-11-11 18:23 ` [Qemu-devel] [PATCH 3/8] ARM: Fix sense of to_integer bit in Neon VCVT float/int conversion Peter Maydell
2010-11-11 18:23 ` [Qemu-devel] [PATCH 4/8] ARM: Return correct result for float-to-integer conversion of NaN Peter Maydell
2010-11-11 19:21 ` Nathan Froyd
2010-11-12 23:08 ` Peter Maydell
2010-11-11 18:23 ` [Qemu-devel] [PATCH 5/8] ARM: Return correct result for single<->double " Peter Maydell
2010-11-11 18:24 ` [Qemu-devel] [PATCH 6/8] ARM: Ignore top 16 bits when doing VCVT from 16 bit fixed point Peter Maydell
2010-11-11 18:24 ` [Qemu-devel] [PATCH 7/8] softfloat: Add float/double to 16 bit integer conversion functions Peter Maydell
2010-11-11 18:24 ` [Qemu-devel] [PATCH 8/8] ARM: Implement VCVT to 16 bit integer using new softfloat routines Peter Maydell
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=20101206165721.GF25904@nightcrawler \
--to=froydnj@codesourcery.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).