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: "Zack Weinberg" <zackw at stanford dot edu>
- Subject: Re: libjava test suite keeps getting stuck
- From: Tom Tromey <tromey at redhat dot com>
- Date: 19 Apr 2001 19:08:45 -0600
- Cc: gcc at gcc dot gnu dot org, java at gcc dot gnu dot org
- References: <20010419101208.E21961@stanford.edu>
- Reply-To: tromey at redhat dot com
>>>>> "Zack" == Zack Weinberg <zackw@stanford.edu> writes:
Zack> While I'm here, why is it that all Java programs are threaded?
That was the easiest way to write the thread code in relatively
abstractly. At least, that's what I recall from when I initially
wrote the thread code in 1998 (I think). The thread code has since
been rewritten, but I don't think that particular decision was
revisited.
Could it be done another way? Sure. However, eventually (probably
meaning gcc 3.1 -- it requires GC 6.0, which will be ready in the
post-3.0 timeframe) we are going to require a separate thread for
finalization anyway. I believe we're forced to do this by Java
semantics. I imagine in the POSIX threads case we will use the main
thread as the finalization thread, since it happens to be sitting
around.
Tom