From owner-freebsd-arch@FreeBSD.ORG Fri Apr 6 19:09:45 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98655106564A for ; Fri, 6 Apr 2012 19:09:45 +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 716CD8FC0C for ; Fri, 6 Apr 2012 19:09:45 +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 DE3B628418; Fri, 6 Apr 2012 12:09:38 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Jason Evans In-Reply-To: <20120405205822.GR9275@thebe.jupiter.sigsegv.be> Date: Fri, 6 Apr 2012 12:09:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3F19C7EF-86D8-4165-AAF1-91424A518333@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> <4F7B98C0.6090209@bluezbox.com> <20120405205822.GR9275@thebe.jupiter.sigsegv.be> To: Kristof Provost X-Mailer: Apple Mail (2.1257) Cc: Oleksandr Tymoshenko , 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 List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2012 19:09:45 -0000 On Apr 5, 2012, at 1:58 PM, Kristof Provost wrote: > On 2012-04-04 22:00:57 (-0700), Jason Evans = wrote: >> On Apr 3, 2012, at 5:41 PM, Oleksandr Tymoshenko wrote: >>> I tested it for MIPS - works fine. Unfortunately I don't have >>> ARM hardware that works with HEAD so can't test ARM part of the = change. >>=20 >> Thanks for testing MIPS. I'm going to just assume that TLS works = everywhere. =20 >> If it doesn't, we'll find out soon enough. =3D) >>=20 > It appears to be rather broken on ARM, at least in combination with > shared libraries. >=20 > [=85] 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? Jason=