This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/21847] ppc64le: expected localentry:0 `pthread_…' ld.so error prevents allocation startup


https://sourceware.org/bugzilla/show_bug.cgi?id=21847

--- Comment #6 from Alan Modra <amodra at gmail dot com> ---
> How does this optimization work?  Does the link editor detect that the
> implementation in libpthread does not require the TOC pointer and then
> activates the optimization?

Yes.

> What happens if we change the implementation later, so that it needs a TOC
> pointer?

That could be solved by versioning.

> I still think this optimization has a general issue with symbol interposition.

True.

> That seems wrong because the libpthread implementation is the real (full)
> implementation.

OK, so I had it back to front.  How is it that an executable or shared library
linked against libpthread.so.0 ends up not using the libpthread.so.0 symbols at
run time?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]