On Wed, Aug 12, 2015 at 6:47 PM, Jeff Law <l...@redhat.com> wrote: > On 08/12/2015 10:24 AM, Ian Lance Taylor wrote: >> >> On Wed, Aug 12, 2015 at 9:21 AM, Tom Tromey <t...@tromey.com> wrote: >>> >>> Jeff> In the past this has stalled on issues like how will >>> asynch-exceptions >>> Jeff> be tested and the like. >>> >>> It seems to me that either there is some other language which needs this >>> -- in which case that language ought to have testing for the feature -- >>> or the feature is only used by gcj, in which case it doesn't matter. >>> >>> Of course is!=ought; but relying on gcj and libjava to provide this >>> small amount of testing seems like a bad cost/benefit tradeoff. >> >> >> Go does use asynchronous exceptions, and has test cases that rely on >> them working. > > If you're comfortable with Go at this point and we have mechanisms in place > to ensure Go only gets built on platforms that support Go, then I think we > should go forward with replacing GCJ with Go.
I think replacing it with Ada makes more sense (still have some systems where a ton of Go tests fail presumably because of too old glibc/kernel). Or just replace it with nothing as effectively neither Go nor Ada are going to be enabled for all primary host platforms (as for Ada you need an Ada host compiler for example). Well. My original idea was to strip down Java testing by basically removing classpath from the picture (to the extent of actually pruning it from the repository apart from maybe java.lang classes). Richard. > Jeff
