public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Haley <aph@redhat.com>
Cc: Harpal Grover <harpal.grover@gmail.com>, java@gcc.gnu.org
Subject: Re: Status of the GJC
Date: Tue, 26 Oct 2010 09:42:00 -0000	[thread overview]
Message-ID: <1288086113.13083.58.camel@springer.wildebeest.org> (raw)
In-Reply-To: <4CC69FA6.4010706@redhat.com>

On Tue, 2010-10-26 at 10:30 +0100, Andrew Haley wrote:
> On 10/26/2010 10:26 AM, Mark Wielaard wrote:
> > On Mon, 2010-10-25 at 17:56 -0400, Harpal Grover wrote:
> >>> It's mostly in maintenance mode.  The compiler itself is pretty solid, but
> >>> the Classpath runtime library isn't being developed very much.  We really
> >>> need to port gcj to use the OpenJDK runtime libraries, which would make
> >>> gcj an excellent product, but so far no-one has had the time to do it.
> >>
> >> I think that's an excellent idea.
> >>
> >> How does one start helping out with that?
> > 
> > There was a project to create a Common Virtual Machine Interface which
> > has some interesting pointers. And Andrew Hughes made enough progress on
> > it to get JamVM to work against it. This project is currently not very
> > active, but seems a good starting point:
> > http://icedtea.classpath.org/wiki/CVMIDiscussion
> > http://fuseyism.com/openjdk/cvmi/
> 
> Hmm.  I would have thought it made more sense to get gcj working with
> the Sun JDK VM interface.  I think we would have done it that way to
> begin with, but the JDK VM interface was secret.

The CVMI pages point to descriptions of the current VM interfaces of
both GNU Classpath (which gcj largely implements) and how Hotspot
interfaces with the OpenJDK class library. It also has a pointer to what
Cacao does (which implements both, plus the CLDC/PhoneME interface). So
even if you don't want to reuse any code from the project itself, it
seems a good starting point if you want to figure out what needs to be
done/changed.

Cheers,

Mark

  reply	other threads:[~2010-10-26  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTik4zH8gptWRLUxq3=ReKimFmz0Sa2ojyamtZYGx@mail.gmail.com>
2010-10-22 20:44 ` Paulo Pinto
2010-10-25 11:35   ` Andrew Haley
2010-10-25 21:56     ` Harpal Grover
2010-10-25 22:02       ` David Daney
2010-10-26  9:26       ` Mark Wielaard
2010-10-26  9:30         ` Andrew Haley
2010-10-26  9:42           ` Mark Wielaard [this message]
2010-11-08 21:18             ` Ian Rogers
2010-11-09 23:42               ` Dr Andrew John Hughes

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=1288086113.13083.58.camel@springer.wildebeest.org \
    --to=mark@klomp.org \
    --cc=aph@redhat.com \
    --cc=harpal.grover@gmail.com \
    --cc=java@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).