Date: Fri, 6 Apr 2012 12:22:02 -0700 From: Jason Evans <jasone@canonware.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: Kristof Provost <kristof@sigsegv.be>, freebsd-arch@freebsd.org Subject: Re: TLS on ARM and MIPS Message-ID: <E7ED7E9C-AA0A-4E63-9D30-9CEFD277D516@canonware.com> In-Reply-To: <4F7F4198.2010705@bluezbox.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E7ED7E9C-AA0A-4E63-9D30-9CEFD277D516>