From: Ludovic Drolez <ldrolez@linbox.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [BUG] QEMU x86_64 SSE bug in modf()
Date: Mon, 15 Jan 2007 15:00:45 +0100 [thread overview]
Message-ID: <45AB890D.9060609@linbox.com> (raw)
In-Reply-To: <20070115115410.GA25141@tapir.sajinet.com.pe>
Carlo Marcelo Arenas Belon wrote:
> On Mon, Jan 15, 2007 at 11:18:01AM +0100, Ludovic Drolez wrote:
>
>>Float to string conversion uses modf() but this function fails under QEMU
>>and SLES 64, as you can see in this small test program below:
>
>
> pressume you mean running SLES 10 64bit as a guest under QEMU here.
> which version of qemu for the host? and what platform/arch?
Hi !
As said in other posts, the guest is a SLES 10 64 bits, the host under a
Debian sarge 32 bits, and I use qemu 0.8.2. I also tried the latest CVS, and
the same bug is present.
> the gcc that is used for the glibc in the guest should be irrelevant if all
> the emulated instructions are correctly compiled in the host and there are no
> bugs on them of course.
Yes, I was thinking of a bug in qemu sse/sse2 emulation.
> the host has to be compiled with gcc 3, gcc 4.x won't work even if it
> compiles.
Compiled with gcc 3.3.5.
Ludovic.
--
Ludovic DROLEZ Linbox / Free&ALter Soft
www.linbox.com www.linbox.org
next prev parent reply other threads:[~2007-01-15 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 10:18 [Qemu-devel] [BUG] QEMU x86_64 SSE bug in modf() Ludovic Drolez
2007-01-15 11:54 ` Carlo Marcelo Arenas Belon
2007-01-15 14:00 ` Ludovic Drolez [this message]
2007-01-15 14:16 ` Julian Seward
2007-01-16 11:22 ` [Qemu-devel] Re: [BUG] QEMU x86_64 SSE bug in modf() + MMX bug Ludovic Drolez
2007-01-16 16:19 ` Ludovic Drolez
2007-01-16 17:50 ` Aurelien Jarno
2007-01-15 12:02 ` [Qemu-devel] [BUG] QEMU x86_64 SSE bug in modf() Thiemo Seufer
2007-01-15 13:54 ` Ludovic Drolez
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=45AB890D.9060609@linbox.com \
--to=ldrolez@linbox.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 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.