From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Xiangyu Hu <libhu.so@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] FMULX should flushes operators to zero when FZ is set.
Date: Tue, 03 Feb 2015 13:44:49 +0000 [thread overview]
Message-ID: <874mr3xg6m.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8pzvqaO3wHG4udQXj8vpaSJD2D33-8==s_GqfDbx2A-g@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 28 January 2015 at 15:57, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 28 January 2015 at 15:54, Alex Bennée <alex.bennee@linaro.org> wrote:
>>> Do we have test cases that trip up here? It would be nice to include
>>> them in our testing as the random nature of RISU has obviously failed to
>>> trip up on this instruction.
>>
>> Risu would probably catch this if we generated and ran test cases
>> which set the FPSCR bits to something other than the default.
>
> This bug is indeed caught by the following risugen:
> ./risugen --numinsns 10000 --pattern "FMULX A64_V" --fpscr 0x01000000
> aarch64.risu FMULX_S3SAME_V_squash.out
>
> (that fpscr value being "set DZ, nothing else".)
>
> Alex, I don't suppose your automation of these tests makes
> it easy to do a complete extra run (or better, just of the
> Neon and FP insn tests) with different FPSCR flags?
I just need to add the additional test sequence and trace to the tarball
and the script should pick it up automatically.
>
> -- PMM
--
Alex Bennée
prev parent reply other threads:[~2015-02-03 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:51 [Qemu-devel] [PATCH] FMULX should flushes operators to zero when FZ is set Xiangyu Hu
2015-01-28 14:54 ` Peter Maydell
2015-01-28 15:42 ` Xiangyu Hu
2015-01-28 15:54 ` Alex Bennée
2015-01-28 15:57 ` Peter Maydell
2015-01-28 16:11 ` Xiangyu Hu
2015-01-28 16:12 ` Claudio Fontana
2015-01-28 16:25 ` Peter Maydell
2015-01-29 19:22 ` Peter Maydell
2015-02-03 13:44 ` 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=874mr3xg6m.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=libhu.so@gmail.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 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.