4.2 + ecj status

Tom Tromey tromey@redhat.com
Mon Oct 23 21:11:00 GMT 2006


I'm going out of town and won't be available to fix 4.2-related bugs
(or do gcj-eclipse merge work) for the next month or so.  So, I
thought I'd post a quick status report so that other folks can pick
things up.

For 4.2 we're in pretty good shape.  There are a few open things I
know of:

* mingw problems, see PR 29477
  I didn't get a chance to look at this; there was a bit of discussion
  on the java-patches list as well.

* PR 25652 -- small GC patch that looked unobjectionable at first
  glance

* PR 29263 -- possible mprec memory leak with patch

* A pending jvmti patch from Kyle -- but that should probably just go
  in 4.3 now.


The gcj-eclipse branch is also in reasonable shape.  We need to work
out what to do about javah for maintainers.  Perhaps the best idea is
to import a new Classpath (which means first making a new Classpath
release) so that we pick up the javah tool.  Then we can "do nothing"
-- just have folks build one before using it.  All that would remain
is to document this.

Aside from that I think only the contrib and gcc/doc changes need
approval before a merge to trunk is possible.

Note that not all of the annotation stuff is ready (and even enums
aren't really working, see PR 29495) -- but this doesn't matter for a
merge, IMO.  I think we only need it to be as good as what we have on
the trunk; we don't need feature completeness for all the new things.

Tom



More information about the Java mailing list