From: Ludovic Drolez <ludovic.drolez@linbox.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [BUG] QEMU x86_64 SSE bug in modf()
Date: Mon, 15 Jan 2007 13:54:59 -0000 [thread overview]
Message-ID: <45AB87AD.3010205@linbox.com> (raw)
In-Reply-To: <20070115120237.GB25395@networkno.de>
Thiemo Seufer wrote:
> Ludovic Drolez wrote:
> [snip]
>
>>Would someone be able to track down this SSE QEMU bug seen only in SLES's
>>modf() function ?
>
>
> Please test if this patch for qemu changes the behaviour.
>
Strange... With this, qemu does not run at all (qemu process stuck with 100%
CPU used).
Ludo.
>
> Thiemo
>
>
> Index: Makefile.target
> ===================================================================
> RCS file: /sources/qemu/qemu/Makefile.target,v
> retrieving revision 1.136
> diff -u -p -r1.136 Makefile.target
> --- Makefile.target 7 Jan 2007 22:04:40 -0000 1.136
> +++ Makefile.target 15 Jan 2007 11:59:15 -0000
> @@ -70,7 +70,7 @@ OP_CFLAGS = -Wall -O2 -g -fno-strict-ali
>
> ifeq ($(ARCH),i386)
> HELPER_CFLAGS+=-fomit-frame-pointer
> -OP_CFLAGS+=-mpreferred-stack-boundary=2 -fomit-frame-pointer
> +OP_CFLAGS+=-fomit-frame-pointer
> ifeq ($(HAVE_GCC3_OPTIONS),yes)
> OP_CFLAGS+= -falign-functions=0 -fno-gcse
> else
>
--
Ludovic DROLEZ Linbox / Free&ALter Soft
www.linbox.com www.linbox.org
prev parent reply other threads:[~2007-01-15 13:54 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 ` [Qemu-devel] " Ludovic Drolez
2007-01-15 14:16 ` [Qemu-devel] " 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 [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=45AB87AD.3010205@linbox.com \
--to=ludovic.drolez@linbox.com \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).