From: Sal <svferro@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org
Subject: Re: GCJ with OpenJDK Java API instead of GNU Classpath
Date: Thu, 07 May 2009 20:24:00 -0000 [thread overview]
Message-ID: <4A0350F1.1080102@gmail.com> (raw)
In-Reply-To: <4A02A70C.3030101@redhat.com>
Andrew Haley wrote:
> It's all GPL + exception, so there are no licence difficulties.
>
> This would be an excellent thing to do, but it would be difficult. In
> particular, class loading and class initialization are done in very
> different ways, and this would all need to be rewritten.
>
> I'd love someone to do this, but I don't want them to be under any illusion
> about how difficult it might be.
>
> Andrew.
>
So it should be challenging then, great :)
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...)
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.
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'm currently trying to make it all the way through the openjdk build
process, to get at the .java sources, and isolate the JNI parts needed
for a working library. Possibly if anyone has already done this let me
know - as it doesn't seem other parts are very critical - (hotspot,
etc.) to get running, since we're just replacing Classpath initially.
Looking forward to any ideas/comments!
Thanks much,
- Sal
next prev parent reply other threads:[~2009-05-07 20:24 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 [this message]
2009-05-08 8:04 ` Robert Schuster
2009-05-08 10:08 ` Andrew Haley
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=4A0350F1.1080102@gmail.com \
--to=svferro@gmail.com \
--cc=aph@redhat.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).