From: "Alex Bennée" <alex.bennee@linaro.org>
To: Michael Clark <mjc@sifive.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmer@sifive.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2
Date: Fri, 09 Mar 2018 15:15:36 +0000 [thread overview]
Message-ID: <87woyljn53.fsf@linaro.org> (raw)
In-Reply-To: <CAHNT7NuBjcngEesbS4XSwn=gw7S8VYVE_e6FjxKuAHfjoWowjQ@mail.gmail.com>
Michael Clark <mjc@sifive.com> writes:
<snip>
>
> BTW - I've integrated the following 3 branches into the riscv tree:
>
> - https://github.com/riscv/riscv-qemu/tree/softfloat-snan-abort-fix
> - https://github.com/riscv/riscv-qemu/tree/riscv-qemu-upstream-v8.2
> - https://github.com/michaeljclark/riscv-qemu/tree/qemu-devel
>
> into our `riscv-all` integration branch, and we're now passing all FPU
> tests, interestingly, including the NaN-boxing of single precision values
> into doubles. We'll need to check that the riscv-tests testsuite is
> exhastive enough... Suprised! I think Richard might have thought about
> our NaN-boxing
> issue or some other sort of magic is going on :-)
>
> - https://github.com/riscv/riscv-qemu/tree/riscv-all
Is the SNaN patch going to get re-posted now it has had a review?
--
Alex Bennée
next prev parent reply other threads:[~2018-03-09 15:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 19:46 [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2 Michael Clark
2018-03-07 0:09 ` Michael Clark
2018-03-07 10:11 ` Richard W.M. Jones
2018-03-07 12:15 ` Michael Clark
2018-03-08 10:02 ` Peter Maydell
2018-03-08 11:10 ` Michael Clark
2018-03-08 11:18 ` Michael Clark
2018-03-08 11:41 ` Michael Clark
2018-03-08 11:52 ` Stefan Hajnoczi
2018-03-08 19:29 ` [Qemu-devel] [patches] " Palmer Dabbelt
2018-03-08 19:53 ` Michael Clark
2018-03-09 14:28 ` Peter Maydell
2018-03-09 14:51 ` Michael Clark
2018-03-09 15:15 ` Alex Bennée [this message]
2018-03-09 15:22 ` Peter Maydell
2018-03-09 16:49 ` Peter Maydell
2018-03-09 20:11 ` Michael Clark
2018-03-09 20:23 ` Michael Clark
2018-03-08 11:48 ` [Qemu-devel] " Daniel P. Berrangé
2018-03-08 20:03 ` Michael Clark
2018-03-08 11:49 ` Paolo Bonzini
2018-03-08 11:19 ` Peter Maydell
2018-03-08 11:36 ` Daniel P. Berrangé
2018-03-08 11:33 ` Daniel P. Berrangé
2018-03-08 11:42 ` Daniel P. Berrangé
2018-03-08 12:25 ` Daniel P. Berrangé
2018-03-08 12:39 ` Paolo Bonzini
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=87woyljn53.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).