summaryrefslogtreecommitdiff
path: root/lib/libc_r/TODO
blob: 75ce8fb8789c2b12a35a7f313509ced5f715c563 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

This is a list of things that still need to be done:

* Add thread stuff to the other archs in libc/arch/; ie change
  some usages of ENTRY to SYSENTRY in some .S files and add
  the new macros to their SYS.h. 

* Find a better way of doing the _sys_aliases stuff; ideally by
  using the linker. jmp's and branches (current implementation) are ugly, but
  I don't want to have to hack ../libc/sys/Makefile.inc just to
  partition the syscalls into wrapped and non-wrapped. The `.set'
  assembler directive just doesn't work as I thought it would.

* Test that thread_init is automatically called on every arch, regardless
  of whether the exe is statically linked or not.

* Alter the objective-C compiler to see if it can use threads.
  It looks like the easy way is to just define CC='cc -pthread'.

* Find all the static buffers in libc and make them per-thread. This
  is not absolutely necessary but incurs no penalty for single-threaded
  operation, and makes life easier & safer for when threads are used.
  On the other hand, it adds a bit more code bloat when you use threads
  and makes openbsd programs non-portable to other OSs with less-nicer
  libraries. If we do the bare posix minimum, we promote portable code.
  
* Look into how netbsd are going with their kernel threads

* Look into how asynchronous I/O can help us. In particular, the
  (unimplemented) aio*() functions.

* Update the libc manual pages to describe the posix re-entrant functions.
  Although this is actually trivial to do, I have to decide on a
  consistent way of adding them - maybe `.Sh THREAD-SAFE FUNCTIONS' ?
  Should look into standards to see what they suggest/did..
  May also need to document "This is not thread-safe" for some library
  functions (yet to be identified).

* Find out where freebsd/netbsd use pread() and pwrite().. i think
  its in the database routines mostly. We will need to rip their code.

* Figure out what to do with the configuration system variables (_SC_*)
  that are defined by POSIX 1003.1c

$OpenBSD: TODO,v 1.4 1998/12/22 22:30:35 d Exp $