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:13:21 -0300 [thread overview]
Message-ID: <2ad73a040804141359052b1a@mail.gmail.com> (raw)
In-Reply-To: <41114D7E.7090201@bellard.org>
Still, there are the graphic routines (which are *painfully slow* when
it goes to VESA mode; console is rather zippy!) and I'm positive the
compiler can optimize FP instructions with SSE or something and/or
reorder/reschedule/etc the instructions in order to ameliorate cache
hits and whatnot.
I still believe it's not a complete waste of time.
On Wed, 04 Aug 2004 22:56:30 +0200, Fabrice Bellard <fabrice@bellard.org> wrote:
> Don't spend your time in using another compiler than gcc : most of the
> time is spent in the generated code, and the quality of this code relies
> on very small functions which are too simple for being optimized better.
>
> Fabrice.
>
--
"A year spent in artificial intelligence is enough to make one believe in God"
Alan J. Perlis
next prev parent reply other threads:[~2004-08-04 21:17 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 [this message]
2004-08-04 21:25 ` Fabrice Bellard
2004-08-04 21:37 ` André Braga
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=2ad73a040804141359052b1a@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 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.