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: Ian Lance Taylor <iant at google dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: Jeff Law <law at redhat 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: Wed, 12 Aug 2015 09:24:06 -0700
- 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>
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.
Ian