This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Avoid privatization of TLS variables
- From: Andrew Haley <aph at redhat dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 27 Sep 2014 09:53:38 +0100
- Subject: Re: Avoid privatization of TLS variables
- Authentication-results: sourceware.org; auth=none
- References: <20140920031617 dot GB2325 at kam dot mff dot cuni dot cz> <20140924175326 dot GE29454 at x4> <20140924181836 dot GE6871 at kam dot mff dot cuni dot cz> <CAKOQZ8xMx8bpXGTXN8pd2RC2T9i31brdQTH13ZWiYdooTVq_aw at mail dot gmail dot com> <54266DC1 dot 9060708 at redhat dot com>
On 27/09/14 08:56, Andrew Haley wrote:
> I may be guilty of missing a crucial point here, but: why do we care
> about having a small limit of static TLS variables?
>
> We surely could allocate, say, a megabyte of static TLS for each
> thread. We already allocate 64M for the thread-local malloc arena,
On 64-bit systems, I mean.
> after all. It doesn't cost anything beyond a little address space.
>
> What am I missing?
>
> Andrew.
>