From owner-freebsd-current Thu Apr 6 12: 9: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 9FDD137BAF5 for ; Thu, 6 Apr 2000 12:08:50 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.0/8.10.0) with ESMTP id e36J8jR13275; Thu, 6 Apr 2000 14:08:45 -0500 (CDT) Date: Thu, 6 Apr 2000 14:08:45 -0500 (CDT) From: Steve Price To: Nate Williams Cc: Daniel Eischen , current@FreeBSD.ORG Subject: Re: signal mask from jmp_buf In-Reply-To: <200004050423.WAA12987@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Nate Williams wrote: # > I am unfamiliar with the JDK port. Does it use FreeBSD native # > threads? # # Nope, see above. If/when FreeBSD gets 'real' kernel threads, it would # be worthwhile to move it to using them, but until that team my suspicion # is the optimzed 'threads' library that is part of the JDK probably is an # easier solution for the JDK. However, Steve may have a different # opinion. :) Actually I was just looking into cleaning the code up a bit and getting it to work on -current again. The version that I compiled many moons ago just coredumps when trying to bootstrap JDK2 builds on -current and I think it has to do with the signals changes. I would like to get a 'real' kernel threads implementation going but it seems that it would be a -current only thing for some time to come, so it might not be worth the effort at this point. At least I don't think I have the energy for it at the moment - too many other interesting projects going on right now. :) Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message