From owner-freebsd-java Sun Feb 24 23:38:35 2002 Delivered-To: freebsd-java@freebsd.org Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by hub.freebsd.org (Postfix) with ESMTP id 6E5BC37B405 for ; Sun, 24 Feb 2002 23:38:33 -0800 (PST) Received: from billh by gnuppy.monkey.org with local (Exim 3.34 #1 (Debian)) id 16fFiN-000159-00; Sun, 24 Feb 2002 23:38:27 -0800 Date: Sun, 24 Feb 2002 23:38:27 -0800 To: freebsd-java@freebsd.org Cc: Bill Huey Subject: HotSpot progress report Message-ID: <20020225073827.GA3969@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i From: Bill Huey Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey Folks, I've been working on various platform dependent parts of HotSpot and have made a lot of progress both piecing together the various non-portable parts and getting a clear mental image of how the VM threading systems works. I've got most of those files compiling cleanly with some left overs with (1) signal delivery per thread and (2) thread stack redzones. With: 1) Read the pthreads implemenation of signal delivery (i'm doing that now) and see how Solaris signaling conventions map over to FreeBSD's stuff semantically. It's bit scary since signals are kind of an amorpheous thingy, but I'm still keeping my head above the water. 2) Stack red-zoning with funky mmap/mprotect trickery and alignment. Which, BTW, I'm thinking about ignoring. Only a handful of compile time errors are left in the platform dependent parts and the rest are pretty superficial. This is a good thing and implies that a kind of "smoke test" might be coming soon. Cross your fingers on that one. There are other things that I have to still worry about it's interrupt and callback framework, but I have most of threading system clearly understood and it's being worked out pretty automatically with a kind of coding unconsciousness that's rare in my personal history with this project. This is a good sign. We'll see. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message