hack to get sysinfo initialized
Jakub Jelinek
jakub@redhat.com
Thu Jan 30 17:17:00 GMT 2003
On Thu, Jan 30, 2003 at 09:13:21AM -0800, David Mosberger wrote:
> >>>>> On Thu, 30 Jan 2003 09:07:11 -0800, Ulrich Drepper <drepper@redhat.com> said:
>
> Uli> LinuxThreads for x86 is meant for compatibility and adding something
> Uli> like this which isn't very often just doesn't seem necessary. If you
> Uli> have a new kernel you want to run a decent thread library.
>
> Sure, I'd love to. I thought the ia64 NPTL bits weren't quite ready yet.
> But yes, it will be nice to have it.
>
> Uli> There is no fundamental problem but it might just open another
> Uli> can of worms (i.e., it needs testing).
>
> I can see that, but unless I'm missing something, the sysinfo member
> is always there in the thread descriptor. Leaving it uninitialized
> seems more dangerous than initializing it with a sane value, no?
The current state of AT_SYSINFO stuff is that NPTL libc/libpthread on i686 uses
it and ld.so from both NPTL and linuxthreads builds set it up.
This is so that ld.so from linuxthreads build can load both linuxthreads
and NPTL libs.
Jakub
More information about the Libc-hacker
mailing list