From: John Hogerhuis <jhoger@gmail.com>
To: Thomas Steffen <steffen.list.account@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] gcc4 host support
Date: Thu, 19 May 2005 15:25:57 -0700 [thread overview]
Message-ID: <dd8f98f40505191525215567@mail.gmail.com> (raw)
In-Reply-To: <d7e2700f05051914033af48d13@mail.gmail.com>
On 5/19/05, Thomas Steffen <steffen.list.account@gmail.com> wrote:
> It as also because C avoids the n by m problem.
>
My point is that you can have your cake and eat it too.
For any given architecture gcc can generate the first approximation by
way of dyngen or dyngen + gcc enhancements.
But once you are past that point gcc for a given arch, gcc isn't
really going to help you any more. So bring on the hand
coding/optimizations. There's no doubt the hand coded stuff would be
at least as good as gcc output. And that's because you can always make
use of what gcc did if you can't think of anything better.
There's really nothing magic going on we're in any danger of losing.
QEMU generates a dynamic code generator dynamically. Clever but lucky
hack, in that it really has no business working (yet it does, but the
lucky part is why it is going to continue to break).
Short of collusion from the gcc folks, I'm saying that it is no less
than the Halting Problem that is staring us in the face here. But no
more than that either. Practically speaking, we can probably go on
like this indefinitely, it just seems unnecessary to me.
The thing that separates QEMU from other projects like Bochs in my
mind is that it dynamically generates code and it has other clever
bits like samba and slirp integration. A high level view is that QEMU
puts a high priority on usability compared to these other projects.
next prev parent reply other threads:[~2005-05-19 22:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:04 [Qemu-devel] [patch] gcc4 host support Paul Brook
2005-05-12 17:00 ` Paul Brook
2005-05-12 22:13 ` Pascal Terjan
2005-05-12 22:25 ` Paul Brook
2005-05-14 7:55 ` Filip Navara
2005-05-14 11:53 ` Paul Brook
2005-05-14 11:56 ` Filip Navara
2005-06-17 4:30 ` [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: " Darryl Dixon
2005-06-17 12:45 ` Paul Brook
[not found] ` <1119013084.5187.4.camel@darrylsfc3box>
2005-06-17 13:02 ` Paul Brook
2005-06-17 22:18 ` David Woodhouse
2005-06-20 1:18 ` Darryl Dixon
2005-05-16 9:41 ` [Qemu-devel] " David Woodhouse
2005-05-17 20:46 ` Paul Brook
2005-05-18 10:06 ` Herbert Poetzl
2005-05-18 16:02 ` Paul Brook
2005-05-18 16:10 ` David Woodhouse
2005-05-18 19:29 ` John Hogerhuis
2005-05-18 20:48 ` Paul Brook
2005-05-18 20:55 ` David Woodhouse
2005-05-18 21:16 ` Paul Brook
2005-05-18 21:29 ` jeebs
2005-05-18 22:37 ` Paul Brook
2005-05-18 23:05 ` Ian Rogers
2005-05-18 22:37 ` Ian Rogers
2005-05-19 7:23 ` Gwenole Beauchesne
2005-05-19 13:20 ` Paul Brook
2005-05-19 14:07 ` Gwenole Beauchesne
2005-05-19 15:44 ` Paul Brook
2005-05-19 18:14 ` Thomas Steffen
2005-05-19 18:52 ` Paul Brook
2005-05-19 19:38 ` Tim Walker
2005-05-19 19:45 ` Paul Brook
2005-05-19 21:03 ` Thomas Steffen
2005-05-19 22:25 ` John Hogerhuis [this message]
2005-05-20 9:59 ` Thomas Steffen
2005-05-20 12:57 ` Paul Brook
2005-05-19 16:18 ` Ian Rogers
2005-05-19 13:47 ` McMullan, Jason
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=dd8f98f40505191525215567@mail.gmail.com \
--to=jhoger@gmail.com \
--cc=jhoger@pobox.com \
--cc=qemu-devel@nongnu.org \
--cc=steffen.list.account@gmail.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).