blob: 39949c28ac8ff23ed7fc337919388c35739992d7 (
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
46
47
48
49
|
-------------------------------------------------
Please note the following caveats when 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 if the extra argument is nonzero.
The standards actually state that if you pass longjmp() a final value
of zero the library should change that to a 1! Presumably the reason
is so people who write broken code can get away with writing
longjmp(buf); or something equally bad. If you pass longjmp() a final
value of 0 you get what you deserve -- setjmp() will happily return 0.
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.
bsd_signal vs sysv_signal:
--------------------------
signal() now defaults to bsd_signal().
|
