[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPLrYEQ94jJOpOJGti-bJ1GpqFgvoz0d-0vB2Z6A1HesyhZT4g@mail.gmail.com>
Date: Sat, 6 Oct 2012 10:17:19 +0200
From: Daniel Cegiełka <daniel.cegielka@...il.com>
To: musl@...ts.openwall.com
Subject: Re: TLS (thread-local storage) support
2012/10/5 Rich Felker <dalias@...ifal.cx>:
> On Thu, Oct 04, 2012 at 11:29:11PM +0200, Daniel Cegiełka wrote:
>> great news! Finally able to compile Go (lang)...
>
> Did Go fail with gcc's emulated TLS in libgcc?
I tested Go with sabotage (with fresh musl). I'll try to do it again...
gcc in sabotage was compiled without support for TLS, so I didn't
expect that it will be successful:
https://github.com/rofl0r/sabotage/blob/master/pkg/gcc4
> My impression is that
> it should usually/always work, but it's just very slow and
> low-quality (lazy allocation). This isn't gcc's fault, just the fact
> that it's impossible to emulate correctly. On the other hand, Go might
> be generating code that accesses TLS directly, in which case the
> emulation may not suffice.
>
> BTW, does Go work with static linking? If not, you might need to wait
> to celebrate until I add the dynamic-linked TLS support...
https://groups.google.com/forum/?fromgroups=#!topic/golang-nuts/N5QCFkXon0M
Daniel
> 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.
