This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/21847] ppc64le: expected localentry:0 `pthread_…' ld.so error prevents allocation startup
- From: "amodra at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 28 Jul 2017 11:28:28 +0000
- Subject: [Bug dynamic-link/21847] ppc64le: expected localentry:0 `pthread_…' ld.so error prevents allocation startup
- Auto-submitted: auto-generated
- References: <bug-21847-131@http.sourceware.org/bugzilla/>
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.