• Home
Name Date Size #Lines LOC

..--

arch-arm/03-May-2024-6,8914,487

arch-x86/03-May-2024-7,4275,684

bionic/03-May-2024-14,0327,855

docs/03-May-2024-514361

include/03-May-2024-11,8176,129

inet/03-May-2024-767394

kernel/03-May-2024-58,66040,719

netbsd/03-May-2024-15,91310,984

private/03-May-2024-2,7651,734

stdio/03-May-2024-7,6373,874

stdlib/03-May-2024-5,8143,871

string/03-May-2024-2,233851

tools/03-May-2024-1,067776

tzcode/03-May-2024-4,1922,924

unistd/03-May-2024-5,2482,627

zoneinfo/03-May-2024-1712

Android.mkD03-May-202414.2 KiB568444

CAVEATSD03-May-20241.4 KiB2719

JamfileD03-May-20249.4 KiB442346

MODULE_LICENSE_BSDD03-May-20240

NOTICED03-May-202418.1 KiB383306

READMED03-May-20242 KiB5434

SYSCALLS.TXTD03-May-202413.1 KiB246231

README

1Welcome to Bionic, Android small and custom C library for the Android platform
2
3Bionic is mainly a port of the BSD C library to our Linux kernel with the
4following additions/changes:
5
6- no support for locales
7- no support for wide chars (i.e. multi-byte characters)
8- its own smallish implementation of pthreads based on Linux futexes
9- support for x86, ARM and ARM thumb CPU instruction sets and kernel interfaces
10
11Bionic is released under the standard 3-clause BSD License
12
13Bionic doesn't want to implement all features of a traditional C library, we only
14add features to it as we need them, and we try to keep things as simple and small
15as possible. Our goal is not to support scaling to thousands of concurrent threads
16on multi-processors machines; we're running this on cell-phones, damnit !!
17
18Note that Bionic doesn't provide a libthread_db or a libm implementation.
19
20
21Adding new syscalls:
22====================
23
24Bionic provides the gensyscalls.py Python script to automatically generate syscall
25stubs from the list defined in the file SYSCALLS.TXT. You can thus add a new syscall
26by doing the following:
27
28- edit SYSCALLS.TXT
29- add a new line describing your syscall, it should look like:
30
31   return_type  syscall_name(parameters)    syscall_number
32
33- in the event where you want to differentiate the syscall function from its entry name,
34  use the alternate:
35
36   return_type  funcname:syscall_name(parameters)  syscall_number
37
38- additionally, if the syscall number is different between ARM and x86, use:
39
40   return_type  funcname[:syscall_name](parameters)   arm_number,x86_number
41
42- a syscall number can be -1 to indicate that the syscall is not implemented on
43  a given platform, for example:
44
45   void   __set_tls(void*)   arm_number,-1
46
47
48the comments in SYSCALLS.TXT contain more information about the line format
49
50You can also use the 'checksyscalls.py' script to check that all the syscall
51numbers you entered are correct. It does so by looking at the values defined in
52your Linux kernel headers. The script indicates where the values are incorrect
53and what is expected instead.
54