public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Sal <svferro@gmail.com>
Cc: java@gcc.gnu.org
Subject: Re: GCJ with OpenJDK Java API instead of GNU Classpath
Date: Fri, 08 May 2009 10:08:00 -0000	[thread overview]
Message-ID: <4A040477.2060500@redhat.com> (raw)
In-Reply-To: <4A0350F1.1080102@gmail.com>

Sal wrote:

> Thanks for all the feedback, I'm glad to hear there are others who seem
> to like the idea as well.  I wasn't sure if this hadn't been started yet
> due to some legal issues, or otherwise.  Sounds like its just something
> that needs a little elbow grease.
> 
> I started some preliminary work - just to get a feel for what might be
> entailed.  What I was thinking as a general plan of attack:
> 
>     1) - Obtain/extract a copy of the Java sources from a
> standard/official Sun release. Just to start working from a clean slate
> since it is an effort towards maximum compatibility. I've noticed that
> not all classes are actually from a simple source-tree extract, some
> are  generated by the build process (so I'm still trying to get through
> this...)

Sure, but once you've done the build you've got everything you need.
Some classes are generated differently, depending on the word size
of the target machine.

>     2) - Isolate a subset of the sources to get gcj-openjdk port
> started. possibly: java.lang.* (and all dependancies) at first, then the
> other fundamental things; java.io.*, java.util.* etc. Although open for
> suggestions here of course.

The core classes and class loaders are all gcj custom and highly
intertwined, so you'd better avoid those.

>     3) - Compile the pieces from 2) with GCJ, add in more packages as
> things build.
> 
>     4) - Somehow, maintain releases for it all as things progress, so
> people can grab current work and collaborate.  I can do so much as to
> zip/upload snapshots when stuff starts working... but maybe others have
> much better ideas or resources here?  I've got a feeling it won't be an
> overnight process, so it would be a big help to allow for as many hands
> on deck as possible.

I think it would probably be best to host this at Sourceforge.  Alternatively,
we could use classpath.org, but that machine is rather heavily loaded
already.

Andrew.

  parent reply	other threads:[~2009-05-08 10:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 20:43 Sal
2009-05-07  9:17 ` Andrew Haley
2009-05-07 11:45   ` Bryce McKinlay
2009-05-07 13:25     ` Andrew John Hughes
2009-05-07 13:43       ` Andrew Haley
2009-05-07 13:50         ` Bryce McKinlay
2009-05-07 20:24   ` Sal
2009-05-08  8:04     ` Robert Schuster
2009-05-08 10:08     ` Andrew Haley [this message]
2009-05-07 16:28 ` Mark Wielaard
2009-05-08 13:47   ` Robert Schuster
2009-05-07 14:31 Chris Gray
2009-05-07 15:29 ` Andrew John Hughes
2009-05-07 16:25   ` Mark Wielaard
2009-05-07 16:32     ` Andrew Haley
2009-05-07 17:10       ` Mark Wielaard
2009-05-07 17:20         ` Andrew Haley
2009-05-07 17:24           ` David Boreham
2009-05-07 17:34             ` Andrew Haley
2009-05-07 17:44           ` Mark Wielaard
2009-05-08  0:22             ` Andrew John Hughes
2009-05-08 10:13               ` Andrew Haley
2009-05-08 11:00                 ` Mark Wielaard

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=4A040477.2060500@redhat.com \
    --to=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=svferro@gmail.com \
    /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).