From owner-freebsd-threads@FreeBSD.ORG Thu Jun 5 01:45:23 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64CA337B401; Thu, 5 Jun 2003 01:45:23 -0700 (PDT) Received: from relay1.cris.net (relay1.cris.net [212.110.128.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BADF43F75; Thu, 5 Jun 2003 01:45:20 -0700 (PDT) (envelope-from ml@phantom.cris.net) Received: from phantom.cris.net (root@phantom.cris.net [212.110.130.74]) by relay1.cris.net (8.12.6/8.12.6) with ESMTP id h55BjrU6076197; Thu, 5 Jun 2003 11:45:53 GMT Received: (from ml@localhost) by phantom.cris.net (8.12.6/8.12.2) id h558qM5I060453; Thu, 5 Jun 2003 11:52:22 +0300 (EEST) (envelope-from ml) Date: Thu, 5 Jun 2003 11:52:22 +0300 From: Alexey Zelkin To: Daniel Eischen Message-ID: <20030605115222.B60385@phantom.cris.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eischen@pcnet.com on Tue, Jun 03, 2003 at 05:48:15AM -0400 X-Operating-System: FreeBSD 4.7-STABLE i386 cc: freebsd-threads@freebsd.org cc: freebsd-java@freebsd.org Subject: Re: Fwd: Re: Native JDK with libthr/libkse X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2003 08:45:23 -0000 hi, On Tue, Jun 03, 2003 at 05:48:15AM -0400, Daniel Eischen wrote: > I was more interested in the statement that "jdk is only guaranteed > to work with libc_r" that one of the Java developers posted. I It only means that I can guarantee correctly working product in environment there're it was tested (i.e. at user threads only level). Don't get me wrong -- I'll be happy to try libthr and libpthread as soon as I'll be able to do it. Local problems here prevents me from complete cvsup right now :-( Also I have to make complete pass of TCK tests (at least VM tests -- more than 8000 testsets) before saying anything. > took it to mean that the implementation of our jdk is geared > towards libc_r (perhaps knowing internal stuff about how libc_r > works). I don't want anything like that to stop us, and we > can add some common APIs to the threads libraries if needed > to support it. I have spent a lot of time to get rid libc_r internals usage in jdk14. pthread_attr_get_np() was a conclusion and allowed me to switch from API to ABI compat mode.