From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Emulation differences, qemu-system-x86_64 vs Athlon64
Date: Thu, 13 Apr 2006 00:15:27 +0100 [thread overview]
Message-ID: <200604130015.27832.jseward@acm.org> (raw)
In-Reply-To: <443D7C9D.8010401@bellard.org>
> I guess the problem comes from the usage of lrintl() on x86_64 in
> fpu/softfloat-native.c, but I cannot test it yet.
It might be that you have to pass in an extra value into those
float -> int conversion routines, which describes what to do if the
conversion is going to overflow. That's because the behaviour is
different depending on the guest architecture. x86/amd64 always
give 0x8000...., whereas ppc gives either 0x8000... or 0x7FFF....
depending on the sign of the argument (IIRC).
J
prev parent reply other threads:[~2006-04-12 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 12:08 [Qemu-devel] Emulation differences, qemu-system-x86_64 vs Athlon64 Julian Seward
2006-04-12 22:18 ` Fabrice Bellard
2006-04-12 23:15 ` Julian Seward [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=200604130015.27832.jseward@acm.org \
--to=jseward@acm.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 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).