From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Performances on Mac OS X
Date: Wed, 4 Aug 2004 18:37:24 -0300 [thread overview]
Message-ID: <2ad73a040804143720a8afcf@mail.gmail.com> (raw)
In-Reply-To: <4111542D.6050201@bellard.org>
What if QEMU uses smarter FP code (for a given architecture) when
emulating the CPU itself? Like always using SSE2, since they have
their own registers, instead of going to the stack of the 387 unit?
Ain't that smarter?
About VESA: one can never have too many compiler optimizations :D
Faster is always good in emulation, and if you can have gains by just
switching compilers, why not use this?
I promise I'll look into the VESA code some time. I'm in love with
QEMU, you know ;D
On Wed, 04 Aug 2004 23:25:01 +0200, Fabrice Bellard <fabrice@bellard.org> wrote:
> FP is not used in QEMU except for the CPU emulation itself, so expect no
> gain. About VESA with the Cirrus VGA card, the code just needs to be
> optimized !
>
> Fabrice.
>
--
"Logic: merely enables one to be wrong with authority"
Doctor Who
next prev parent reply other threads:[~2004-08-04 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 15:43 [Qemu-devel] Re: Performances on Mac OS X Joshua Root
2004-08-04 16:31 ` Ben Pfaff
2004-08-04 17:32 ` [Qemu-devel] Intel compiler (was Re: Performances on Mac OS X) André Braga
2004-08-04 18:50 ` [Qemu-devel] Re: Performances on Mac OS X Roine Gustafsson
2004-08-04 20:56 ` Fabrice Bellard
2004-08-04 21:13 ` André Braga
2004-08-04 21:25 ` Fabrice Bellard
2004-08-04 21:37 ` André Braga [this message]
2004-08-04 21:42 ` Lindsay Mathieson
2004-08-04 21:47 ` Laurent Amon
2004-08-04 21:55 ` André Braga
2004-08-13 10:17 ` Joshua Root
2004-08-13 12:14 ` Joe Batt
2004-08-15 4:39 ` dguinan
-- strict thread matches above, loose matches on Subject: below --
2004-08-13 10:55 Joshua Root
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=2ad73a040804143720a8afcf@mail.gmail.com \
--to=meianoite@gmail.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).