This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: libjava test suite keeps getting stuck
- To: Tom Tromey <tromey at redhat dot com>
- Subject: Re: libjava test suite keeps getting stuck
- From: Jeff Sturm <jsturm at one-point dot com>
- Date: Fri, 20 Apr 2001 21:08:43 -0400 (EDT)
- cc: Zack Weinberg <zackw at Stanford dot EDU>, gcc at gcc dot gnu dot org, java at gcc dot gnu dot org
On 20 Apr 2001, Tom Tromey wrote:
> ideally we wouldn't need std::terminate. We don't use it anyway --
> all our exceptions, including those from destructors in these classes,
> should be Java exceptions, handled via the normal Java methods. So
> instead it would be nice to somehow tell this to g++ so that this call
> is never generated.
Yeah. Having thought about it though, this is really a special case.
Cleanups don't throw or catch exceptions, so they are agnostic to the
exception type. Also cleanups aren't used by gcj anywhere other from
synchronization. The c++ frontend doesn't distinguish JvSynchronize
from other c++ classes because it's not a java class. So it applies the
usual cleanup rules.
As strange as it would be to see the std namespace creeping into libjava,
it hardly seems worthwhile to change anything else. Though I didn't see
std::terminate mentioned in Zack's message, so I ought to consider what's
different in the new EH.
Jeff