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: Wed, 18 May 2005 23:37:43 +0100	[thread overview]
Message-ID: <200505182337.43559.paul@codesourcery.com> (raw)
In-Reply-To: <036001c55bf0$a9aa34f0$334d21d1@organiza3bfb0e>

> I am definetly out of my depth here, but... Speaking of GCJ's JIT...
>
> Sometime back, Ian Rogers here brought up the PearColator project at:
> http://www.binarytranslator.org/
>
> ***
> I have been working on an open source Java based PowerPC emulator based
> around a JVM's optimising compiler. If you have long running server like
> workloads then I have found the performance is approaching QEMU fast
> whilst having memory supported by a page based system. However, the
> system is a lot less sophisticated - booting operating systems and being
> a generic emulator is a distant reality. I have created a website at
> http://www.binarytranslator.org/ or
> http://www.cs.man.ac.uk/apt/projects/jamaica/tools/PearColator/ . I'm
> sure some people would be interested in this and may feel like they want
> to contribute. I'm happy to oblige and to share with QEMU. Thanks,
> ***
>
> Looks like he's getting at least some tolerable numbers...

I know I'd seen something like this before, thanks for reminding me.

There are several issues with PearColator/RVM:

- It's written in java. qemu is written in C, so a lot of porting would be 
required to get anything working.
- The best benchmark results are half the speed of qemu, and ten times slower 
appears to be a more typical result.
- I can't see an any way of doing an incremental transition. My code generator 
coexists with dyngen, allowing a gentle migration away from dyngen.

Paul

  reply	other threads:[~2005-05-18 22:43 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 [this message]
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=200505182337.43559.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).