From owner-freebsd-threads@FreeBSD.ORG  Mon Jun 16 16:31:25 2003
Return-Path: <owner-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 148AB37B401
	for <threads@freebsd.org>; Mon, 16 Jun 2003 16:31:25 -0700 (PDT)
Received: from hqemgate00.nvidia.com (hqemgate00.nvidia.com [216.228.112.144])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2EE7343FAF
	for <threads@freebsd.org>; Mon, 16 Jun 2003 16:31:24 -0700 (PDT)
	(envelope-from gareth@nvidia.com)
Received: from mail-sc-0.nvidia.com (Not Verified[172.16.217.105])
	id <BA00300d28>; Mon, 16 Jun 2003 16:34:11 -0700
Received: by mail-sc-0.nvidia.com with Internet Mail Service (5.5.2653.19)
	id <MJR3V7TD>; Mon, 16 Jun 2003 16:30:50 -0700
Message-ID: <2D32959E172B8F4D9B02F68266BE421401A6D7E1@mail-sc-3.nvidia.com>
From: Gareth Hughes <gareth@nvidia.com>
To: 'Daniel Eischen' <eischen@pcnet.com>,
	Julian Elischer <julian@elischer.org>
Date: Mon, 16 Jun 2003 16:30:49 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
cc: threads@freebsd.org
cc: zander@mail.minion.de
cc: Andy Ritger <ARitger@nvidia.com>
Subject: RE: NVIDIA and TLS
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2003 23:31:25 -0000

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.

-- 
Gareth Hughes (gareth@nvidia.com)
OpenGL Developer, NVIDIA Corporation