[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] tls_model("initial-exec") attribute prevents dynam
From: |
Milian Wolff |
Subject: |
Re: [Libunwind-devel] tls_model("initial-exec") attribute prevents dynamic loading of libunwind via dlopen() |
Date: |
Mon, 07 May 2018 23:01:56 +0200 |
On Montag, 7. Mai 2018 22:08:26 CEST Bert Wesarg wrote:
> On Mon, May 7, 2018 at 9:27 PM, Milian Wolff <address@hidden> wrote:
> > On Mittwoch, 2. Mai 2018 13:23:03 CEST Bert Wesarg wrote:
> >> Dear Milian,
> >>
> >> I tried to remember why we choose the initial-exec model, but could
> >> not found any reasons. By reading
> >> https://www.akkadia.org/drepper/tls.pdf again, I would say
> >> "local-exec" is the right way to go here. Which should be the default
> >> for 'static' variables anyway. Can you please confirm, that this works
> >> for you. Its just important, that there are no calls to
> >> __tls_get_addr() in the asm output.
> >
> > No, with the default I do see __tls_get_addr in the asm output (i.e.
> > matches in Gparser.o). So probably, the default isn't OK to be used
> > everywhere.
> Sorry, that were two questions:
>
> 1) Does "local-exec" works with dlopen for you?
See my follow-up mail, it doesn't compile.
> 2) Does the default model produces __tls_get_addr in the asm output?
>
> I assume you answered only the second one?
>
> Bert
>
> > Thanks
--
Milian Wolff
address@hidden
http://milianw.de
signature.asc
Description: This is a digitally signed message part.
Re: [Libunwind-devel] tls_model("initial-exec") attribute prevents dynamic loading of libunwind via dlopen(), Dave Watson, 2018/05/02