This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: Stable release?
- To: Godmar Back <gback at cs dot utah dot edu>
- Subject: Re: Stable release?
- From: Tom Tromey <tromey at cygnus dot com>
- Date: Wed, 16 Feb 2000 20:59:43 -0800 (PST)
- Cc: green at redhat dot com, aph at pasanda dot cygnus dot co dot uk, mdw at cs dot berkeley dot edu, bryce at albatross dot co dot nz, java-discuss at sourceware dot cygnus dot com
- References: <200002161759.JAA09820@hoser.cygnus.com><200002161815.LAA25313@faith.cs.utah.edu>
>>>>> "Godmar" == Godmar Back <gback@cs.utah.edu> writes:
Godmar> I'd like that. Ideally, fix the problems on RH 5.2 in tree.c
Godmar> before you do that and/or the problem with -fno-builtin. (Or
Godmar> whatever else problem I'll encounter in the future...)
Yeah, this is exactly the problem with us blessing any snapshot...
That said, we don't have to officially bless anything. If somebody
out there (Matt for instance :-) has found a certain snapshot to work,
they're free to publicize it here. I'd even point people at such a
thing, in response to bug report, probably.
Godmar> Maybe it would be good to install a bonsai/tinderbox like
Godmar> scheme that continuously recompiles and tests on various
Godmar> platforms and flags bad checkins? In particular, I'm
Godmar> concerned about checkins from the non-gcj part of egcs that
Godmar> inadvertently affect the gcj front-end.
Yes, us too -- especially now that the C++ compiler is getting a
facelift.
I would like to see an automatic test system set up. gcc already has
something along these lines, but it doesn't test libgcj. (Hopefully
it will once libgcj is put into the gcc cvs tree -- one of the goals
of the classpath merge and relicensing.)
We actually have what I think is a good plan for doing this sort of
testing, in a mostly automatic, distributed way. The big problem is
finding time to implement it. Anybody interested in implementing this
sort of thing is welcome to step forward...
Tom