qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH for-3.1 0/7] target/ppc fp cleanups
Date: Wed, 04 Jul 2018 17:48:15 +0100	[thread overview]
Message-ID: <87r2kj7xrk.fsf@linaro.org> (raw)
In-Reply-To: <36142D7E-604F-428F-BF51-4AE9DC64FC0B@gmail.com>


Programmingkid <programmingkidx@gmail.com> writes:

>> On Jul 4, 2018, at 11:39 AM, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>>
>> Programmingkid <programmingkidx@gmail.com> writes:
>>
>>>> On Jul 4, 2018, at 10:15 AM, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>>
>>>>
>>>> Richard Henderson <richard.henderson@linaro.org> writes:
>>>>
>>>>>
>>>>> Anyway, all of this has been broken long enough that it'll need to
>>>>> wait til next devel cycle before anything further gets done.
>>>>
>>>> When it gets done should we add some explicit ppc tests to tests/tcg/ppc
>>>> like we did with arm64 fcvt or would it be worth spending more time on
>>>> the general purpose FP test suite Emilio was working on as part of his
>>>> hard-float series?
>>>
>>> My vote goes to adding PowerPC specific tests. I already made some and sent them to the list a couple of days ago. A general purpose floating point test suite would probably not be able to test things like PowerPC floating point flags.
>>>
>>> I'm not certain how we would add floating point tests to QEMU. I'm
>>> guessing it would involve some kind of bootable image file that would
>>> load and run the tests. Hopefully there is an easier way to implement
>>> testing.
>>
>> You don't need system tests - this is all testable from linux-user. See
>> tests/tcg/arm/fcvt.c and the .ref files in arm and aarch64 directories.
>> Assuming the test isn't insane (like test-i386-fprem) we can just add a
>> reference output recorded on know good hardware.
>
> My hope is to make testing the floating point unit as easy as 'make
> test' or maybe 'make fp-test'.

That would be "make check-tcg"


--
Alex Bennée

      reply	other threads:[~2018-07-04 16:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 15:17 [Qemu-devel] [PATCH for-3.1 0/7] target/ppc fp cleanups Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 1/7] target/ppc: Enable fp exceptions for user-only Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 2/7] target/ppc: Honor fpscr_ze semantics and tidy fdiv Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 3/7] target/ppc: Tidy helper_fmul Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 4/7] target/ppc: Tidy helper_fadd, helper_fsub Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 5/7] target/ppc: Tidy helper_fsqrt Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 6/7] target/ppc: Honor fpscr_ze semantics and tidy fre, fresqrt Richard Henderson
2018-07-03 15:17 ` [Qemu-devel] [PATCH 7/7] target/ppc: Use non-arithmetic conversions for fp load/store Richard Henderson
2018-07-05 16:31   ` Programmingkid
2018-07-05 16:48     ` Richard Henderson
2018-07-05 16:51       ` Programmingkid
2018-07-06  1:03         ` David Gibson
2018-07-06  9:03       ` [Qemu-devel] [Qemu-ppc] " Mark Cave-Ayland
2018-08-05 11:41         ` Mark Cave-Ayland
2018-08-06  1:33           ` Richard Henderson
2018-07-04  3:31 ` [Qemu-devel] [PATCH for-3.1 0/7] target/ppc fp cleanups David Gibson
2018-07-04 13:42   ` Programmingkid
2018-07-05  0:09     ` David Gibson
2018-07-04 14:15 ` Alex Bennée
2018-07-04 14:49   ` Programmingkid
2018-07-04 15:39     ` Alex Bennée
2018-07-04 16:23       ` Programmingkid
2018-07-04 16:48         ` Alex Bennée [this message]

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=87r2kj7xrk.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.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).