* __libc_internal_tsd_*
@ 2002-09-02 5:06 Jakub Jelinek
2002-09-02 12:45 ` __libc_internal_tsd_* Roland McGrath
0 siblings, 1 reply; 2+ messages in thread
From: Jakub Jelinek @ 2002-09-02 5:06 UTC (permalink / raw)
To: Ulrich Drepper, Roland McGrath; +Cc: Glibc hackers
Hi!
Just wondering whether it wouldn't be better to reduce the number of
__libc_internal_tsd_* variables out there for dynamic libraries (ATM
we have 3 copies, ld.so, libc.so and libpthread.so) and instead
just use one in ld.so (perhaps with rtld_hidden* aliases for ld.so,
so it doesn't need the .got entries).
__pthread_initialize_minimal needs to be called anyway and thus could
fill it in...
This would be IMHO especially good for
prelink, since now __libc_internal_tsd_* are always conflicts (at least
in ld.so, but in threaded programs in libc.so too).
If you don't think this is a good idea, we should at least put
__libc_internal_tsd_address in a separate source from the rest of no-tsd.c
(no-tsda.c?), so that ld.so which doesn't use it at all doesn't export it.
Well, if we do what I suggested above, it would make sense to split it too,
since then __libc_internal_tsd_address can have its home in libc.so and
thus loads from it can go through an hidden alias (which is bypassing
one indirection (.got))...
What do you think?
Jakub
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: __libc_internal_tsd_*
2002-09-02 5:06 __libc_internal_tsd_* Jakub Jelinek
@ 2002-09-02 12:45 ` Roland McGrath
0 siblings, 0 replies; 2+ messages in thread
From: Roland McGrath @ 2002-09-02 12:45 UTC (permalink / raw)
To: Jakub Jelinek; +Cc: Ulrich Drepper, Glibc hackers
That sounds reasonable to me.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-09-02 19:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-02 5:06 __libc_internal_tsd_* Jakub Jelinek
2002-09-02 12:45 ` __libc_internal_tsd_* Roland McGrath
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).