Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2012 09:44:16 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Ed Schouten <ed@80386.nl>
Cc:        freebsd-arch@FreeBSD.org, David Chisnall <theraven@FreeBSD.org>, Marius Strobl <marius@alchemy.franken.de>
Subject:   Re: NO_TLS flag for public headers
Message-ID:  <D5C04950-6F94-49F6-8613-A8B9684A63A3@bsdimp.com>
In-Reply-To: <20120210105726.GO1860@hoeg.nl>
References:  <58175263-109E-4FF0-BB29-E0331C01DCD5@FreeBSD.org> <20120208215122.GA28769@alchemy.franken.de> <20120210105726.GO1860@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help

On Feb 10, 2012, at 3:57 AM, Ed Schouten wrote:

> Hi Marius,
>=20
> * Marius Strobl <marius@alchemy.franken.de>, 20120208 22:51:
>> See lib/libc/stdlib/malloc.c, arm and mips currently are the only
>> supported FreeBSD architectures that have no support for TLS.
>=20
> Just out of curiosity, what is needed to make TLS work? Is it just the
> lack of support by our toolchain or is there also stuff on our side =
that
> needs to be done?

On MIPS it is partially a toolchain issue and partially a kernel issue.  =
I believe the kernel issue has been fixed recently...  I'm not sure =
what's left on the toolchain side.

Warner




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5C04950-6F94-49F6-8613-A8B9684A63A3>