From owner-freebsd-threads@FreeBSD.ORG Mon Jul 18 05:15:01 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 6D71C16A41C for ; Mon, 18 Jul 2005 05:15:01 +0000 (GMT) (envelope-from d.ayers@inode.at) Received: from mail.turbocat.net (mail.turbocat.net [213.133.116.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id D828943D48 for ; Mon, 18 Jul 2005 05:15:00 +0000 (GMT) (envelope-from d.ayers@inode.at) Received: by mail.turbocat.net (Postfix, from userid 1002) id C086D422EC43; Mon, 18 Jul 2005 07:14:57 +0200 (CEST) Received: from [10.0.0.13] (83-65-214-98.work.xdsl-line.inode.at [83.65.214.98]) by mail.turbocat.net (Postfix) with ESMTP id AD5F9422EC2A; Mon, 18 Jul 2005 07:14:56 +0200 (CEST) Message-ID: <42DB3A6B.90309@inode.at> Date: Mon, 18 Jul 2005 07:13:15 +0200 From: David Ayers User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1 X-Accept-Language: en MIME-Version: 1.0 To: Pascal Hofstee References: <1121453983.672.15.camel@synergy.charterpipeline.net.lan> <1121662853.701.10.camel@synergy.charterpipeline.net.lan> In-Reply-To: <1121662853.701.10.camel@synergy.charterpipeline.net.lan> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: [PATCH] Re: GNUstep, libobjc and threading X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 05:15:01 -0000 Pascal Hofstee schrieb: > On Fri, 2005-07-15 at 12:00 -0700, Pascal Hofstee wrote: > > I just realized it may be possible to do the whole _thr_initial dance > inside the actual _get_curthread() function ... if that turns out to be > the case .. perhaps that location would be more suitable than this > 'stopgap'. FWIW, personally I think your patch is the correct approach. Putting the initialization in _get_curthread() may be a 'stopgap' but it may hit the performance unduly. In the case of the API functions, I believe the correctness issue trumps performance issues. Cheers, David Ayers