qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] gcc4 host support
Date: Thu, 19 May 2005 16:44:54 +0100	[thread overview]
Message-ID: <200505191644.54916.paul@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505191546220.5807@thalys.mandrakesoft.com>

On Thursday 19 May 2005 15:07, Gwenole Beauchesne wrote:
> On Thu, 19 May 2005, Paul Brook wrote:
> > Do you have a URL? Neither google nor freshmeat.net turn up anything
> > useful.
>
> Sorry, here it is:
> <http://svn.valgrind.org/vex/trunk/> (used for valgrind 3.0)
> <http://www.valgrind.org/devel/cvs_svn.html>

This looks interesting, the problem is how to get it to cooperate with the 
dyngen code. We hold some guest CPU state (or at least intermediate state) in 
host registers.

I guess it depends wether you're willing to throw out dyngen and implement 
everything in one go.  I'm currently trying an incremental approach (as 
suggested by Fabrice), in which case I think a custom JIT is pretty much the 
only option.

> > It would be nice if we could use some sort of portable JIT library,
> > however I think in reality a few qemu specific hacks(most of which we
> > already use with dyngen) and a relatively dumb JIT are going to perform
> > better.
>
> What about using GNU lightning as an intermediate solution? It has a
> RISC-style ISA with up to 6 registers exposed. It's "dumb" (no
> optimization) but it's good at generating code. I think it matches most
> the "synthetic instruction" approach of dyngen.

I don't think GNU lightning really gains us much. We'd still have to do the 
hard bits (optimization, register allocation, assigning stack slots, etc). 
The actual native code generation (which is what lightning gives you) is only 
a few hundred lines of code.

Paul

  reply	other threads:[~2005-05-19 15:48 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 [this message]
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=200505191644.54916.paul@codesourcery.com \
    --to=paul@codesourcery.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).