From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Cc: Tim Olson <tim@io.com>
Subject: Re: [Qemu-devel] SSE 'maxps' instruction bug?
Date: Wed, 14 Mar 2007 02:21:22 +0000 [thread overview]
Message-ID: <200703140221.22432.jseward@acm.org> (raw)
In-Reply-To: <41decffa258b38db92ab799d6c2990bc@io.com>
> 0.9.0, or that the compiler/host combination used to build the qemu
> binary Julian is running generated bad code for the float compares.
I used gcc 3.4.6 bootstrapped as normal ('make bootstrap; make install')
on a 64-bit machine. If it is qemu generating bad code due to variations
in gcc behaviour, that's another argument in favour of scrapping the gcc
3.X based backend and using a self contained, handwritten insn selector
and register allocator.
J
next prev parent reply other threads:[~2007-03-14 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 14:50 [Qemu-devel] SSE 'maxps' instruction bug? Julian Seward
2007-03-12 16:27 ` malc
2007-03-13 14:03 ` Julian Seward
2007-03-13 23:07 ` Tim Olson
2007-03-14 2:21 ` Julian Seward [this message]
2007-03-16 18:07 ` Rob Landley
2007-03-16 18:10 ` Julian Seward
2007-03-16 20:17 ` Rob Landley
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=200703140221.22432.jseward@acm.org \
--to=jseward@acm.org \
--cc=qemu-devel@nongnu.org \
--cc=tim@io.com \
/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).