This is the mail archive of the
mailing list for the libc-ports project.
On Mon, May 08, 2006 at 10:29:58AM +0100, Will Newton wrote:
> Can anyone enlighten me as to what setting FLOATING_STACKS for a
> LinuxThreads port actually means? The comments seem to suggest that it
> should be used in conjunction with some kernel facility (TLS of some
> kind?) but I'm not entirely clear whether my (as yet unreleased)
> LinuxThreads port should set this flag or not.
It has very little platform-independent meaning. Basically, if you
have to search the list of stacks to figure out where a thread is, you
shouldn't define it. And it must be constant at compile time. If you
can define THREAD_SELF, then you should also define FLOATING_STACKS.
For instance, if there's a dedicated register in which you can record
the thread pointer, then you can use this.
I really don't recommend writing a new LinuxThreads port at this late
date, though. NPTL is a bit harder to port, but well worthwhile.