platform_bionic/libc
Nick Kralevich 1c88362021 am 8717c3db: am 7a34ed2b: Merge "clean up FORTIFY_SOURCE handling."
* commit '8717c3db2f864226bb68c7e26ad73fcff1212b31':
  clean up FORTIFY_SOURCE handling.
2012-12-05 08:25:37 -08:00
..
arch-arm Remove (near-)duplicate definitions of size_t and ssize_t. 2012-11-29 17:25:23 -08:00
arch-mips Remove (near-)duplicate definitions of size_t and ssize_t. 2012-11-29 17:25:23 -08:00
arch-x86 Merge "Replace .S version of x86 crtfiles with .c version" 2012-11-30 10:07:19 -08:00
bionic clean up FORTIFY_SOURCE handling. 2012-12-04 15:27:30 -08:00
docs Remove obsolete CHANGES.TXT and ISSUES.TXT. 2012-10-17 11:33:59 -07:00
include FORTIFY_SOURCE: fortify strrchr 2012-12-03 10:39:16 -08:00
kernel am 940e4c9d: am f61e5020: msm_mdp: Update header for 4 layer support 2012-11-29 14:28:29 -08:00
netbsd Add search domain to dns interface data. 2012-11-13 11:50:57 -08:00
private am 8717c3db: am 7a34ed2b: Merge "clean up FORTIFY_SOURCE handling." 2012-12-05 08:25:37 -08:00
stdio Define DEFFILEMODE and friends 2012-11-29 11:53:33 -08:00
stdlib More upstream NetBSD upgrades. 2012-10-23 16:05:09 -07:00
string clean up FORTIFY_SOURCE handling. 2012-12-04 15:27:30 -08:00
tools Verify architecture neutral syscall numbers 2012-11-29 12:04:23 -08:00
tzcode am 85819efe: am f2b3ac95: Merge "Fix recovery: don\'t assert if there\'s no tzdata." 2012-10-25 15:16:44 -07:00
unistd More upstream NetBSD upgrades. 2012-10-23 16:05:09 -07:00
upstream-dlmalloc Fix build warning of initialization but no use. 2012-09-06 09:59:13 -07:00
upstream-netbsd libc: Fix alphasort() signature (and implementation). 2012-10-29 07:44:27 -07:00
wchar Move non-upstream code into the libc/bionic directory. 2012-10-01 17:35:49 -07:00
zoneinfo Upgrade to tzdata2012j. 2012-11-26 14:51:39 -08:00
Android.mk am 7beaa502: am 16c61f08: Merge "Reduce the exposure of the __set_errno implementation detail." 2012-11-30 14:46:50 -08:00
CAVEATS auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
MODULE_LICENSE_BSD auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
NOTICE Update generate-NOTICE.py to know about tzdata. 2012-10-19 14:55:19 -07:00
README Add an 's and a . to the bionic/libc README. 2009-07-23 17:41:47 -07:00
SYSCALLS.TXT [MIPS] Fix the MIPS getsid system call 2012-11-29 12:05:25 -08:00

Welcome to Bionic, Android's small and custom C library for the Android
platform.

Bionic is mainly a port of the BSD C library to our Linux kernel with the
following additions/changes:

- no support for locales
- no support for wide chars (i.e. multi-byte characters)
- its own smallish implementation of pthreads based on Linux futexes
- support for x86, ARM and ARM thumb CPU instruction sets and kernel interfaces

Bionic is released under the standard 3-clause BSD License

Bionic doesn't want to implement all features of a traditional C library, we only
add features to it as we need them, and we try to keep things as simple and small
as possible. Our goal is not to support scaling to thousands of concurrent threads
on multi-processors machines; we're running this on cell-phones, damnit !!

Note that Bionic doesn't provide a libthread_db or a libm implementation.


Adding new syscalls:
====================

Bionic provides the gensyscalls.py Python script to automatically generate syscall
stubs from the list defined in the file SYSCALLS.TXT. You can thus add a new syscall
by doing the following:

- edit SYSCALLS.TXT
- add a new line describing your syscall, it should look like:

   return_type  syscall_name(parameters)    syscall_number

- in the event where you want to differentiate the syscall function from its entry name,
  use the alternate:

   return_type  funcname:syscall_name(parameters)  syscall_number

- additionally, if the syscall number is different between ARM and x86, use:

   return_type  funcname[:syscall_name](parameters)   arm_number,x86_number

- a syscall number can be -1 to indicate that the syscall is not implemented on
  a given platform, for example:

   void   __set_tls(void*)   arm_number,-1


the comments in SYSCALLS.TXT contain more information about the line format

You can also use the 'checksyscalls.py' script to check that all the syscall
numbers you entered are correct. It does so by looking at the values defined in
your Linux kernel headers. The script indicates where the values are incorrect
and what is expected instead.