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