https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5dfbc9e4903c0121140f2
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793119
Title:
Thanks a lot :-)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793119
Title:
Wrong floating-point emulation on AArch64 with FPCR set to zero
Status in QEMU:
Fix Committed
Bug description:
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793119
Title:
Wrong floating-point emulation on AArch64 with FPCR set to zero
Status
Neither will be sufficient in my use case. IEEE-754 conformance is
essential. Thank you for the hints.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793119
Title:
Wrong floating-point emulation
On 18 September 2018 at 19:18, Emilio G. Cota
<1793...@bugs.launchpad.net> wrote:
> Not yet. There should be a fix before 3.1 is released.
>
> Both 2.12 and 3.0 have this bug, so you might want to consider using
> 2.11 until the bug gets fixed.
On the other hand 2.11 has a different set of
Not yet. There should be a fix before 3.1 is released.
Both 2.12 and 3.0 have this bug, so you might want to consider using
2.11 until the bug gets fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Thanks for the update. Is there a fix/patch for the issue?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793119
Title:
Wrong floating-point emulation on AArch64 with FPCR set to zero
Status in
Thanks for your report. This is a known regression on our implementation
of f64_div, introduced by cf07323d49 ("fpu/softfloat: re-factor div",
2018-02-21).
We are working on improving FP tests to limit regressions, e.g. see this
thread, where the bug you report is first mentioned:
