This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCC 3.4 Release Status (2003-12-16)
- From: Tom Tromey <tromey at redhat dot com>
- To: mark at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, geoffk at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: 16 Dec 2003 11:03:17 -0700
- Subject: Re: GCC 3.4 Release Status (2003-12-16)
- References: <200312161732.hBGHWGNG019615@doubledemon.codesourcery.com>
- Reply-to: tromey at redhat dot com
>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:
Mark> What is the realistic status of Java maintenance at this point?
Mark> Is it reasonable to look for Java regressions to get fixed, or
Mark> do we not have enough personpower to do that? For the last
Mark> several releases, we do not seem to have been able to fix Java
Mark> PRs very effectively.
Generally we seem to be in ok shape for this release. My search shows
8 bugs targeted for 3.4. Michael Koch has done some work recently on
Java 3.4 bugs. 13056 will be fixed shortly and there is a patch
pending for 12001. So two are being fixed, 4 are on my to-do list
(verifier bugs and -jar bugs), leaving just 2 unclaimed bugs (13273
and 12980).
Nightly testing shows gcj doing pretty well. It also successfully
runs eclipse, a major test.
Last release I think a couple regressions went unfixed just because
they were platform-specific for a platform that none of the main gcj
hackers use.
Historically, not all java bugs are equal, either. We have
comparatively more library hackers than compiler hackers. Front end
bugs tend to go unfixed for long periods of time.
Finding manpower to work on gcj 3.4 bugs is a bit of a problem. I'll
find out whether RH can have somebody (hopefully me :-) work on this
for a bit.
Tom