bionic/libc
Ben Cheng 55fc93a909 am 8f149da0: am b3b1ab62: Merge "Adding memcpy tuned for Cortex-A15."
* commit '8f149da08dc3125824e168f8d29613be80b2085c':
  Adding memcpy tuned for Cortex-A15.
2013-03-01 10:26:52 -08:00
..
arch-arm Adding memcpy tuned for Cortex-A15. 2013-03-01 10:40:50 +00:00
arch-mips Fix the pthread_setname_np test. 2013-02-15 12:08:59 -08:00
arch-x86 Stop advertising rindex(3), which is both deprecated and unimplemented. 2013-02-21 17:39:06 -08:00
bionic Reimplement scandir(3). 2013-02-25 13:14:31 -08:00
docs Remove obsolete CHANGES.TXT and ISSUES.TXT. 2012-10-17 11:33:59 -07:00
include unistd.h: don't include sys/capability.h 2013-03-01 10:10:55 -08:00
kernel Fix mako builds. Do not merge. 2013-02-20 12:47:58 -08:00
netbsd Update getnameinfo.c, remove dead code, and fix error reporting. 2013-02-13 13:11:11 -08:00
private Reimplement scandir(3). 2013-02-25 13:14:31 -08:00
stdio Define DEFFILEMODE and friends 2012-11-29 11:53:33 -08:00
stdlib stdlib: atexit: include <sys/cdefs.h> 2013-02-16 21:23:27 +05:30
string clean up FORTIFY_SOURCE handling. 2012-12-04 15:27:30 -08:00
tools Remove dead code from gensyscalls.py. 2013-02-07 14:07:00 -08:00
tzcode Revert "DO NOT MERGE Revert "Add the libcutils localtime_tz and mktime_t extensions to bionic."" 2013-01-16 10:34:33 -08:00
unistd __progname should be const char*, not char*. 2013-02-07 12:06:44 -08: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 Reimplement scandir(3). 2013-02-25 13:14:31 -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.