From owner-freebsd-current@FreeBSD.ORG  Wed Mar 24 04:57:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F03B616A4CE; Wed, 24 Mar 2004 04:57:55 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9412943D45; Wed, 24 Mar 2004 04:57:55 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i2OCvptf024092;
	Wed, 24 Mar 2004 07:57:51 -0500 (EST)
Date: Wed, 24 Mar 2004 07:57:51 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Doug Rabson <dfr@nlsystems.com>
In-Reply-To: <200403240914.10447.dfr@nlsystems.com>
Message-ID: <Pine.GSO.4.10.10403240757080.22672-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Marcel Moolenaar <marcel@xcllnt.net>
cc: freebsd-current@freebsd.org
cc: Julian Elischer <julian@elischer.org>
cc: FreeBSD current users <current@freebsd.org>
Subject: Re: SF Bay area hackfest
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2004 12:57:56 -0000

On Wed, 24 Mar 2004, Doug Rabson wrote:

> On Wednesday 24 March 2004 00:36, Julian Elischer wrote:
> > The linker and dynamic linker are expected to 'plonk' snippets of
> > machine dependent code into whereever an access to TLS is being made,
> > depending on whether the access is to the same statically linked
> > module or another module, loaded at run time, or the 'main' module.
> > The "wheres" for these 'runtime code-insertions' are marked by the
> > toolchain.
> 
> I'll take the dynamic linker if no-one else wants it. I'm not coming to 
> the bay area to do it though :-). I've been seriously considering 
> putting in symbol version support too.

Yes, please!

-- 
Dan Eischen