[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121017004253.GW254@brightrain.aerifal.cx>
Date: Tue, 16 Oct 2012 20:42:53 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: TLS (thread-local storage) support
On Wed, Oct 17, 2012 at 02:08:11AM +0200, boris brezillon wrote:
> >> I agree. This should be made optional. But if we don't compile libc
> >> with fsplit-stack (-fnosplit-stack).
> >> Each call to a libc func from an external func compiled with split
> >> stack may lead to a 64K stack chunk alloc.
> >
> > Where does this allocation take place from? There should simply be a
> > way to inhibit it.
> In the linker (gold linker).
Well gold isn't running at runtime. I assume you mean it _arranges_
for this allocation to take place somehow, and that's what I'm
wondering about whether there's a way to avoid.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
