From owner-freebsd-arch@FreeBSD.ORG Mon Apr 2 18:13:46 2012 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2651106564A for ; Mon, 2 Apr 2012 18:13:46 +0000 (UTC) (envelope-from jasone@canonware.com) Received: from canonware.com (10140.x.rootbsd.net [204.109.63.53]) by mx1.freebsd.org (Postfix) with ESMTP id B45298FC12 for ; Mon, 2 Apr 2012 18:13:46 +0000 (UTC) Received: from [172.25.16.174] (unknown [173.252.71.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by canonware.com (Postfix) with ESMTPSA id 6F6D42841A for ; Mon, 2 Apr 2012 11:04:27 -0700 (PDT) From: Jason Evans Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 2 Apr 2012 11:04:26 -0700 Message-Id: <2FF97057-905D-4F02-9138-75680ABC6202@canonware.com> To: arch@freebsd.org Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) Cc: Subject: TLS on ARM and MIPS X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 18:13:46 -0000 I've been working on integrating jemalloc back into FreeBSD's libc, and = ran into the lack of TLS on ARM and MIPS. Is this something that's = likely to be addressed soon? If not, I'm going to have to modify libthr = to deal with TSD bootstrapping issues -- FreeBSD's pthreads = implementation *loves* to call malloc. =3D( While I'm asking about TLS, it's worth asking whether any of the other = platforms still lack TLS support for non-PIC binaries. If so, that will = force the TSD issue anyway. Thanks, Jason=