From: John Reiser <jreiser@BitWagon.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on Fedora Core 3 (Linux 2.6.9+), glibc-2.3.3
Date: Mon, 20 Dec 2004 07:48:26 -0800 [thread overview]
Message-ID: <41C6F44A.7060408@BitWagon.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412201613160.6637@wgmdd8.biozentrum.uni-wuerzburg.de>
> silly question: why don't you use inline assembly to make those two
> functions?
>
The calls are not execution-time critical (fewer than 10 calls).
They are complexity, platform, and developer-time critical.
More time will be spent by developers and future maintainers
than the total machine cycles spent executing the code,
over all the machines in the world, ever. So making the
developer+maintainer tasks simple and quick is more important
than cycle- or byte-efficiency.
--
next prev parent reply other threads:[~2004-12-20 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 5:11 [Qemu-devel] qemu on Fedora Core 3 (Linux 2.6.9+), glibc-2.3.3 John Reiser
2004-12-19 10:03 ` Hetz Ben Hamo
2004-12-19 13:55 ` John Reiser
2004-12-19 14:35 ` John Reiser
2004-12-19 22:47 ` Fabrice Bellard
2004-12-20 0:54 ` John Reiser
2004-12-20 15:13 ` Johannes Schindelin
2004-12-20 15:48 ` John Reiser [this message]
2004-12-22 6:55 ` Darrin Ritter
2004-12-22 15:05 ` John Reiser
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=41C6F44A.7060408@BitWagon.com \
--to=jreiser@bitwagon.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).