[src/trunk]: src/lib/libpthread pthread_kill() was implemented, remove from list

[jdolecek <jdolecek%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/2321a83f0d0a
branches:  trunk
changeset: 542766:2321a83f0d0a
user:      jdolecek <jdolecek%NetBSD.org@localhost>
date:      Thu Feb 06 09:55:47 2003 +0000

description:
pthread_kill() was implemented, remove from list
pthread_cond_timedwait() now works even before SA initialization, but some
other routines do not; update the paragraph for this

diffstat:

 lib/libpthread/TODO |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (24 lines):

diff -r c523c3578076 -r 2321a83f0d0a lib/libpthread/TODO
--- a/lib/libpthread/TODO       Thu Feb 06 09:46:46 2003 +0000
+++ b/lib/libpthread/TODO       Thu Feb 06 09:55:47 2003 +0000
@@ -1,8 +1,9 @@
 Bugs to fix:
 
-- pthread_cond_timedwait() doesn't work if SA's aren't running yet,
-  because the alarm system isn't up and running. It would be weird to
-  use them that way, but it's perfectly legal.
+- some blocking routines (like sem_wait()) don't work if SA's aren't
+  running yet, because the alarm system isn't up and running or there is no
+  thread context to switch to. It would be weird to use them that
+  way, but it's perfectly legal.
 - There is a race between pthread_cancel() and
   pthread_cond_broadcast() or pthread_exit() about removing an item
   from the sleep queue. The locking protocols there need a little
@@ -27,7 +28,6 @@
 
 
 Interfaces/features to implement:
-- pthread_kill()
 - pthread_atfork()
 - priority scheduling
 - libc integration: