bionic/libc
Elliott Hughes be11de2b52 am 5fb409b7: Merge "Bring the NOTICE files back up to date."
# Via Elliott Hughes (1) and Gerrit Code Review (1)
* commit '5fb409b7b0b0a4ecca5fd2a6c7dc5ce421f6b7cf':
  Bring the NOTICE files back up to date.
2013-01-29 16:42:04 -08:00
..
arch-arm Use the NetBSD <sys/exec_elf.h>. 2013-01-29 15:02:50 -08:00
arch-mips Use the NetBSD <sys/exec_elf.h>. 2013-01-29 15:02:50 -08:00
arch-x86 Use the NetBSD <sys/exec_elf.h>. 2013-01-29 15:02:50 -08:00
bionic Don't collect useless stack frames; do demangle C++ symbols. 2013-01-29 09:56:31 -08:00
docs Remove obsolete CHANGES.TXT and ISSUES.TXT. 2012-10-17 11:33:59 -07:00
include Use the NetBSD <sys/exec_elf.h>. 2013-01-29 15:02:50 -08:00
kernel am f09f6db5: Merge "Use the NetBSD <sys/exec_elf.h>." 2013-01-29 16:26:10 -08:00
netbsd More upstream NetBSD upgrades. 2012-10-23 16:05:09 -07:00
private am 244bee5b: Merge "bionic_auxv.h: fix #define conflict" 2013-01-22 13:38:53 -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 arm syscall : for eabi call_default don't use stack 2013-01-16 14:53:37 +01:00
tzcode Revert "DO NOT MERGE Revert "Add the libcutils localtime_tz and mktime_t extensions to bionic."" 2013-01-15 11:12:18 -08: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 Our strcoll(3) is no different from NetBSD's, so take exactly theirs. 2013-01-22 15:10:19 -08: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 Our strcoll(3) is no different from NetBSD's, so take exactly theirs. 2013-01-22 15:10:19 -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 Bring the NOTICE files back up to date. 2013-01-29 16:25:06 -08:00
README Add an 's and a . to the bionic/libc README. 2009-07-23 17:41:47 -07:00
SYSCALLS.TXT Add signalfd call to bionic 2013-01-10 13:14:46 -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.