From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Running QEMU on FreeBSD
Date: Mon, 31 May 2004 02:24:24 +0100 [thread overview]
Message-ID: <1085966664.347.8.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40BA7E1A.5080005@fabianowski.de>
On Mon, 2004-05-31 at 01:36, Bartosz Fabianowski wrote:
> I just discovered another problem with your patch.
>
> Before applying your patch, I was using my own hack that resorted to
> normal precision doubles for FPU emulation. This resulted in incorrect
> rounding as could be easily seen when running Windows Update. The total
> number of megabytes to download was something like 10.99999999999998.
> Obviously, something had gone wrong with precision and rounding.
>
> However, after I have applied your patch, which imports from Linux the
> functions required to use long doubles, the situation got worse. The
> total number of megabytes to be downloaded by Windows Update is now
> shown as NaN. I know from previous installs that it should be a
> moderately sized number, something such as 10 or 20 megabytes. So it's
> not the rounding of an immensely large number or of a ridiculously small
> one that is going wrong. There is some other issue surfacing here that
> makes a perfectly normal-sized floating point number become a NaN.
Replace the rintl() function in target-i386/op.c with the following:
CPU86_LDouble rintl(CPU86_LDouble __x) {
register CPU86_LDouble __result;
__asm __volatile__ ("frndint" : "=t" (__result) : "0" (__x));
return __result;
}
> It's 2:30am here in Europe right now and I won't investigate this
> further tonight. But if you have time to, maybe you can have a look and
> see if you can find the source of this problem.
>
> - Bartosz
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> FLAGS (\Seen))
--
next prev parent reply other threads:[~2004-05-31 1:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 21:25 [Qemu-devel] Running QEMU on FreeBSD Antony T Curtis
2004-05-29 21:39 ` Bartosz Fabianowski
2004-05-29 21:50 ` Antony T Curtis
2004-05-29 21:58 ` Bartosz Fabianowski
2004-05-29 22:09 ` Antony T Curtis
2004-05-29 22:24 ` Bartosz Fabianowski
2004-05-29 23:09 ` Antony T Curtis
2004-05-30 3:53 ` Antony T Curtis
2004-05-30 7:25 ` Markus Niemistö
2004-05-30 9:50 ` Antony T Curtis
2004-05-30 14:41 ` Bartosz Fabianowski
2004-05-30 17:27 ` Antony T Curtis
2004-05-30 18:57 ` Bartosz Fabianowski
2004-05-30 20:09 ` Antony T Curtis
2004-05-31 0:36 ` Bartosz Fabianowski
2004-05-31 1:24 ` Antony T Curtis [this message]
2004-05-31 1:42 ` Bartosz Fabianowski
2004-05-31 1:59 ` Kyle Hayes
2004-05-31 12:15 ` Bartosz Fabianowski
2004-05-31 13:22 ` Antony T Curtis
2004-05-31 9:38 ` Antony T Curtis
2004-05-31 20:36 ` Bartosz Fabianowski
2004-05-31 13:54 ` Antony T Curtis
2004-05-31 20:31 ` Bartosz Fabianowski
2004-05-31 22:15 ` Antony T Curtis
2004-05-31 22:56 ` Brion Vibber
2004-05-31 23:01 ` Bartosz Fabianowski
2004-06-02 23:18 ` qemu port (was: Re: [Qemu-devel] Running QEMU on FreeBSD) Juergen Lock
2004-06-02 23:54 ` [Qemu-devel] Re: qemu port Bartosz Fabianowski
2004-06-03 17:10 ` Gianni Tedesco
2004-06-04 18:44 ` Juergen Lock
2004-06-05 21:04 ` [Qemu-devel] FreeSBIE timer (was: Re: qemu port) Juergen Lock
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=1085966664.347.8.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.com \
--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).