From: Paul Brook <paul@codesourcery.com>
To: jhoger@pobox.com
Cc: David Woodhouse <dwmw2@infradead.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] gcc4 host support
Date: Wed, 18 May 2005 21:48:50 +0100 [thread overview]
Message-ID: <200505182148.50628.paul@codesourcery.com> (raw)
In-Reply-To: <dd8f98f40505181229380aeb65@mail.gmail.com>
On Wednesday 18 May 2005 20:29, John Hogerhuis wrote:
> This all feels wrong in general. The changes should either be adding
> some facility to gcc which permits QEMU to use it in this way (gcc is
> an open source project after all, so it's at least a possibility),
Are you willing to write and maintain the gcc patches necessary to do this?
qemu is pretty much the only think that has this particular set of
requirelents (the return instruction must be the last instruction in the
function). The fact is qemu is abusing the output of gcc in ways that were
never guaranteed to work.
> or we should generate the dynamic code generator once with whatever
> version of GCC and make that part of the build, perhaps even letting
> it diverge (i.e. add enhancements/optimizations directly to the
> generated assembly).
IMHO That's not really an option. The whole point of dyngen is to avoid having
to write and maintain big chunks of assembly for every single target.
It's been said before that the long-term solution is to [incrementally] remove
dyngen altogether, and replace it with a had-written code generator.
I've discussed this in a bit more detail with Fabrice, and have an
almost-working prototype implementation. When I get something that actually
works I'll post it to the list for comments.
Paul
next prev parent reply other threads:[~2005-05-18 20:58 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 [this message]
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
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=200505182148.50628.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=dwmw2@infradead.org \
--cc=jhoger@pobox.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).