This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Ian Lance Taylor <iant at google dot com>, Tom Tromey <tom at tromey dot com>, Uros Bizjak <ubizjak at gmail dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, GCJ-patches <java-patches at gcc dot gnu dot org>, Andrew Haley <aph at redhat dot com>
- Date: Thu, 13 Aug 2015 12:00:49 +0200
- Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
- Authentication-results: sourceware.org; auth=none
- References: <CAFULd4YCSbA_2V8jNF1QtcM8b4EF8mJzTD7PyU9ETZ-uSyemsw at mail dot gmail dot com> <CAFULd4bj7q=U+yHrd=+U9NgB=wMQtarvAEw-uAW9xL6SC09keQ at mail dot gmail dot com> <55CA44C8 dot 7000209 at redhat dot com> <87mvxxdxys dot fsf at tromey dot com> <55CB5BB7 dot 4090703 at redhat dot com> <871tf81nrk dot fsf at tromey dot com> <CAKOQZ8x03_3HwKc3Dm8qXyxnhnYezHidq88R+VMkL7T04OpPqg at mail dot gmail dot com> <55CB7885 dot 6090900 at redhat dot com>
On Wed, Aug 12, 2015 at 6:47 PM, Jeff Law <law@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 <tom@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