Date: Fri, 6 Apr 2012 12:09:38 -0700 From: Jason Evans <jasone@canonware.com> To: Kristof Provost <kristof@sigsegv.be> Cc: Oleksandr Tymoshenko <gonzo@bluezbox.com>, freebsd-arch@freebsd.org Subject: Re: TLS on ARM and MIPS Message-ID: <3F19C7EF-86D8-4165-AAF1-91424A518333@canonware.com> In-Reply-To: <20120405205822.GR9275@thebe.jupiter.sigsegv.be> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 5, 2012, at 1:58 PM, Kristof Provost wrote: > On 2012-04-04 22:00:57 (-0700), Jason Evans <jasone@canonware.com> = 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F19C7EF-86D8-4165-AAF1-91424A518333>