From owner-freebsd-arch@FreeBSD.ORG  Fri Apr  6 19:22:04 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1E847106566B
	for <freebsd-arch@freebsd.org>; Fri,  6 Apr 2012 19:22:04 +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 EA7B08FC08
	for <freebsd-arch@freebsd.org>; Fri,  6 Apr 2012 19:22:03 +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 8CBD028418;
	Fri,  6 Apr 2012 12:22:03 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Jason Evans <jasone@canonware.com>
In-Reply-To: <4F7F4198.2010705@bluezbox.com>
Date: Fri, 6 Apr 2012 12:22:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7ED7E9C-AA0A-4E63-9D30-9CEFD277D516@canonware.com>
References: <2FF97057-905D-4F02-9138-75680ABC6202@canonware.com>
	<4F79F020.9070504@freebsd.org>
	<3C11DB18-1C43-446E-A0BC-FC15C6126819@canonware.com>
	<4F7A170E.8020209@bluezbox.com>
	<BE64B52D-B1BA-4107-8D14-D4FAF2C62350@canonware.com>
	<4F7B98C0.6090209@bluezbox.com>
	<C2ED9FBB-DA2E-4F35-A0E4-8AF8148FEB1D@canonware.com>
	<20120405205822.GR9275@thebe.jupiter.sigsegv.be>
	<3F19C7EF-86D8-4165-AAF1-91424A518333@canonware.com>
	<4F7F4198.2010705@bluezbox.com>
To: Oleksandr Tymoshenko <gonzo@bluezbox.com>
X-Mailer: Apple Mail (2.1257)
Cc: Kristof Provost <kristof@sigsegv.be>, freebsd-arch@freebsd.org
Subject: Re: TLS on ARM and MIPS
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jasone@freebsd.org
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 19:22:04 -0000

On Apr 6, 2012, at 12:18 PM, Oleksandr Tymoshenko wrote:
> On 06/04/2012 12:09 PM, Jason Evans wrote:
>> On Apr 5, 2012, at 1:58 PM, Kristof Provost wrote:
>>> It appears to be rather broken on ARM, at least in combination with
>>> shared libraries.
>>>=20
>>> [=85]
>>=20
>> Thanks for testing, Kristof.  It's good to know that there are =
problems on ARM, but now I'm not sure what to do about committing the =
updated malloc.  I don't have the time or the hardware to make TLS =
reliable on ARM.  Do I commit the malloc patch and let someone who cares =
about ARM fix TLS after the fact?  Or do I wait an indefinite amount of =
time to let solid TLS support materialize?
>=20
> I'm working on this issue. I hope it will be resolved in a matter of
> days.

Awesome, that's great news.  Thank you.

Jason=