From: "Jim C. Brown" <jma5@umd.edu>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] patch for qemu with newer gcc-3.4.x (support repz retq optimization for amd processors correctly)
Date: Wed, 9 Nov 2005 22:35:46 -0500 [thread overview]
Message-ID: <20051110033546.GA1424@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20051110014404.GC2321@mail.shareable.org>
On Thu, Nov 10, 2005 at 01:44:04AM +0000, Jamie Lokier wrote:
> >
> > The use of gcc to generate the back end in QEMU's early days was a
> > clever way to get the project up and running quickly. But surely
> > now it would be better to transition to a handwritten backend, so
>
> It should be trivial to take the _currently_ generated GCC code for
> all the architectures QEMU is commonly built on, and just distribute
> that code with the QEMU source.
>
You mean convert the code with gcc 3 into asm, and then distribute that?
I'm no expert, but I would imagine such a solution would be quite brittle.
That's assuming one can make gcc 3 assembly code work with gcc 4 (5?) code
to form a single object file.
> Then it would be independent of future changes to GCC.
Well, someone would still need to maintain all those assembly files.
Or else keep an old copy of gcc 3 around to regenerate them whenever needed.
>
> I understand a handwritten backend is already being written. But
> until a proper one is done, wouldn't that serve as a useful stopgap?
>
I believe the current version works - but it doesn't implement every possible
op yet. For now, it relies on dyngen to produce the missing ops (until they are
replaced with the hand coded version).
> -- Jamie
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-11-10 3:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 19:17 [Qemu-devel] patch for qemu with newer gcc-3.4.x (support repz retq optimization for amd processors correctly) Igor Kovalenko
2005-11-09 19:45 ` Paul Brook
2005-11-09 19:51 ` Igor Kovalenko
2005-11-10 1:33 ` Julian Seward
2005-11-10 1:44 ` Jamie Lokier
2005-11-10 3:35 ` Jim C. Brown [this message]
2005-11-11 7:59 ` John R. Hogerhuis
2005-11-10 1:54 ` Jim C. Brown
2005-11-10 22:28 ` Igor Kovalenko
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=20051110033546.GA1424@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=jamie@shareable.org \
--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.