diff options
author | H. Peter Anvin <hpa@zytor.com> | 2002-08-17 03:04:46 +0000 |
---|---|---|
committer | H. Peter Anvin <hpa@zytor.com> | 2002-08-17 03:04:46 +0000 |
commit | 56df17a094f4a1b8e2e02e5be2dcd60afd52e764 (patch) | |
tree | 4197f401faf790c446c9ac057b3c7569e556d83a | |
parent | 6ce345a4a0ee58897e2ff9a00c406ab75085de0c (diff) | |
download | klibc-56df17a094f4a1b8e2e02e5be2dcd60afd52e764.tar.gz |
Caveats for programmers.klibc-0.45
-rw-r--r-- | CAVEATS | 45 | ||||
-rw-r--r-- | klibc/CAVEATS | 45 |
2 files changed, 90 insertions, 0 deletions
diff --git a/CAVEATS b/CAVEATS new file mode 100644 index 0000000000000..91f736fdb16c0 --- /dev/null +++ b/CAVEATS @@ -0,0 +1,45 @@ + ------------------------------------------------- + Please note the following caveats to using klibc: + ------------------------------------------------- + +optimization: +------------- + +Compiling with -O0 is not supported. It may or may not work; please +use -O1 if you want to do maximize debuggability. + +Compiling with -O0 is more likely to work on gcc 3. + + +setjmp()/longjmp(): +------------------- + +setjmp() and longjmp() *do not* save signal state. sigsetjmp() and +siglongjmp() *do* save the signal mask -- regardless of the value of +the extra argument. + + +stdio: +------ + +Only a small subset of the stdio functions are implemented. Those +that are implemented do not buffer, although they *do* trap EINTR or +short read/writes and iterate. + +_fread() and _fwrite(), which take only one size argument (like +read/write), but do handle EINTR/short return are also available. + + +namespaces: +----------- + +klibc frequently includes headers in other headers in a way that +exposes more symbols than POSIX says they should. "Live with it." + + +theading: +--------- + +klibc is not thread-safe. Consequently, clone() or any of the +pthreads functions are not included. + diff --git a/klibc/CAVEATS b/klibc/CAVEATS new file mode 100644 index 0000000000000..91f736fdb16c0 --- /dev/null +++ b/klibc/CAVEATS @@ -0,0 +1,45 @@ + ------------------------------------------------- + Please note the following caveats to using klibc: + ------------------------------------------------- + +optimization: +------------- + +Compiling with -O0 is not supported. It may or may not work; please +use -O1 if you want to do maximize debuggability. + +Compiling with -O0 is more likely to work on gcc 3. + + +setjmp()/longjmp(): +------------------- + +setjmp() and longjmp() *do not* save signal state. sigsetjmp() and +siglongjmp() *do* save the signal mask -- regardless of the value of +the extra argument. + + +stdio: +------ + +Only a small subset of the stdio functions are implemented. Those +that are implemented do not buffer, although they *do* trap EINTR or +short read/writes and iterate. + +_fread() and _fwrite(), which take only one size argument (like +read/write), but do handle EINTR/short return are also available. + + +namespaces: +----------- + +klibc frequently includes headers in other headers in a way that +exposes more symbols than POSIX says they should. "Live with it." + + +theading: +--------- + +klibc is not thread-safe. Consequently, clone() or any of the +pthreads functions are not included. + |