qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@pobox.com>
To: 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: Thu, 10 Nov 2005 23:59:43 -0800	[thread overview]
Message-ID: <1131695984.6973.17.camel@aragorn> (raw)
In-Reply-To: <20051110014404.GC2321@mail.shareable.org>

On Thu, 2005-11-10 at 01:44 +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.
> 
> Then it would be independent of future changes to GCC.
> 
> I understand a handwritten backend is already being written.  But
> until a proper one is done, wouldn't that serve as a useful stopgap?
> 
> -- Jamie
> 


I you poke around in the archives, this idea was raised before (by me,
maybe). I think it would work, but I didn't hear a lot of enthusiasm for
it. I think it would also open the door for hand-tweaking critical areas
for performance.

Paul Brook has another take, and the benefit of his is you can look at
real life code to see how it will work.

-- John.

  parent reply	other threads:[~2005-11-11  7:59 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
2005-11-11  7:59         ` John R. Hogerhuis [this message]
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=1131695984.6973.17.camel@aragorn \
    --to=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).