This is the mail archive of the mailing list for the libc-ports 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]


On 5/8/06, Daniel Jacobowitz <> wrote:

Hi Daniel,

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.

OK, thanks for the information. I'm far from an expert on LinuxThreads internals so I'm rather feeling my way with this implementation - I initially had defined FLOATING_STACKS but not THREAD_SELF. This lead to rapid death, which I think is to be expected.

For instance, if there's a dedicated register in which you can record
the thread pointer, then you can use this.

What are the ideal requirements of such a register? Reserved in the ABI? Our ABI is still tentatively open to modification so this may be a future possibility.

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.

Unfortunately we are focussing on Linux 2.4 for the near future so NPTL would appear to be a non-starter.

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