From owner-freebsd-threads@FreeBSD.ORG Mon Jun 16 22:59:22 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 5833037B401 for ; Mon, 16 Jun 2003 22:59:22 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id D008A43F3F for ; Mon, 16 Jun 2003 22:59:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2injaq3.dialup.mindspring.com ([165.121.171.67] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19S9V1-00034S-00; Mon, 16 Jun 2003 22:59:19 -0700 Message-ID: <3EEEADF5.6DC76F9F@mindspring.com> Date: Mon, 16 Jun 2003 22:58:13 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gareth Hughes References: <2D32959E172B8F4D9B02F68266BE421401A6D7E1@mail-sc-3.nvidia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f75b8175ffdaf6a0ca4897b4cf105796548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: threads@freebsd.org cc: zander@mail.minion.de cc: 'Daniel Eischen' cc: Andy Ritger cc: Julian Elischer Subject: Re: NVIDIA and TLS 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: Tue, 17 Jun 2003 05:59:22 -0000 Gareth Hughes wrote: > On Mon, 16 Jun 2003, Daniel Eischen wrote: > > Right. It just seems wrong to me to be able to insert __thread > > after every global variable in a library and instantly make > > it thread-safe. > > Why, exactly? Surely, from a programming point of view, this is > exactly what you want -- a transparent way to access your thread > local data. No, what you want first and foremost is your code to compile and run on all platforms, without limiting your market by relying on defacto language extensions that have not been explicitly and intentionally standardized by a recognized standards body. -- Terry