This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should we remove java from the default bootstrap languages?
- From: Tom Tromey <tromey at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: Diego Novillo <dnovillo at google dot com>, gcc at gcc dot gnu dot org, Tom Tromey <tromey at redhat dot com>
- Date: Fri, 20 Jun 2008 10:41:05 -0600
- Subject: Re: Should we remove java from the default bootstrap languages?
- References: <485A66B5.9030406@google.com> <485A68D0.4000600@redhat.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
Diego> I posted this question to the SC panel at the GCC Summit today. I
Diego> wanted to consider the possibility of making java a non-default language.
Andrew> If this were to happen it would break repeatedly.
Yeah, our experience back when libgcj was not in the tree was not very
good. It broke all the time.
But, I am actually ok with having it be disabled by default, provided
that regressions affect gcj are treated seriously: fixed in a timely
way by the person causing the regression, or, if not, letting gcj
maintainers start the patch-reversion clock.
If we make this change I'll set up an auto-tester on the compile farm
that builds gcj along with everything else. I think this would
provide a pretty reasonable compromise. Ideally we could find a PPC
box somewhere to do this as well -- anyone have some cycles to spare?
What do you think of this?
Another idea is to build jc1 but not libgcj. That would prevent a
certain (more minor) class of breakage.
What is behind my thinking here is just the fact that gcj development
has dropped off quite a bit.
Tom