Re: gcj and jikes

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Geert" == Geert Bevin <gbevin at uwyn dot com> writes:

Geert> I think you touch an important point here. I'd like to start
Geert> contributing to gcj and lend a hand where it's possible, though
Geert> I have no idea at all where to start and what needs to be done.

The easiest place to contribute is the class libraries.  You could
either look through Gnats for bugs to fix, or you could look at the
nightly status page and pick a library that is unimplemented, and
implement it.

Getting involved with the compiler is harder, since there's more to
learn before you can start contributing, and the internals aren't as
well documented as the class libraries.  But if that's what you'd
rather work on, you can again look through Gnats, or you can just try
to compile some large program and then see if you can figure out how
to fix the bugs that come up.  For instance, any error you run into
while building Eclipse will be a gcj bug.

Tom