From: Joshua Root <z3022016@student.unsw.edu.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Performances on Mac OS X
Date: Fri, 13 Aug 2004 20:17:45 +1000 [thread overview]
Message-ID: <p06020400bd42441b6675@[192.168.0.2]> (raw)
In-Reply-To: <41114D7E.7090201@bellard.org>
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.
What if more than one instruction worth of C were chained together
before being compiled? Would that make more optimisable code? Could
this even be done at runtime? Translation time would be greatly
increased of course, making caching even more important.
Is this technically feasible? Or would my time be better spent
writing a hand optimised code translator? ;)
Cheers,
Josh
next prev parent reply other threads:[~2004-08-13 11:00 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
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 [this message]
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='p06020400bd42441b6675@[192.168.0.2]' \
--to=z3022016@student.unsw.edu.au \
--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).