platform_bionic/libc
David 'Digit' Turner f1a39dce60 libc: Fix typo that broke NDK compatibility.
The function must be named __atomic_cmpxchg, not __android_cmpxchg.
This typo broke existing prebuilt binaries (they couldn't be loaded
at runtime anymore).

Change-Id: I25ca7d18329817f0056e616a0409113269ad7b1f
2011-11-23 14:38:36 +01:00
..
arch-arm libc: Fix typo that broke NDK compatibility. 2011-11-23 14:38:36 +01:00
arch-sh Add tgkill syscall. 2011-11-18 16:40:48 -08:00
arch-x86 Merge "libc: provide atomic operations will full barriers for NDK apps." 2011-11-22 02:10:06 -08:00
bionic Merge "Add tgkill syscall." 2011-11-21 13:13:26 -08:00
docs libc: Fix the definition of SIGRTMAX 2010-12-20 15:58:06 +01:00
include Merge "libc: provide atomic operations will full barriers for NDK apps." 2011-11-22 02:10:06 -08:00
inet Fix build. 2011-06-09 13:03:17 -07:00
kernel Add auto-exposure/auto-white balance lock support to soc2030 image 2011-10-31 11:42:18 -07:00
netbsd Send both A and AAAA queries if all probes fail. 2011-09-28 22:38:08 -07:00
private bionic: Do not use <sys/atomics.h> for platform code. 2011-11-16 16:28:10 +01:00
regex Remove compiler warnings when building Bionic. 2010-06-22 17:51:41 -07:00
stdio libc: speed-up flockfile()/funlockfile() 2011-11-15 13:16:42 +01:00
stdlib Enable functional DSO object destruction 2011-07-07 22:51:43 +02:00
string Fix strerror(3) for errno 0. 2011-05-13 10:54:34 -07:00
tools Update to tzdata2011m. 2011-10-24 10:52:14 -07:00
tzcode am ac56f5ca: Merge "strftime: Use snprintf() instead of sprintf()" 2011-06-23 06:13:53 -07:00
unistd libc: popen: work around data corruption 2011-09-17 15:22:21 -07:00
wchar wchar.h: improve wchar_t support in Bionic 2010-06-15 07:04:41 -07:00
zoneinfo Update to tzdata2011n. 2011-10-31 14:11:32 -07:00
Android.mk Merge "libc: provide atomic operations will full barriers for NDK apps." 2011-11-22 02:10:06 -08:00
CAVEATS auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
Jamfile 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 Clean up NOTICE files. 2010-10-19 15:12:40 -07:00
README Add an 's and a . to the bionic/libc README. 2009-07-23 17:41:47 -07:00
SYSCALLS.TXT Add tgkill syscall. 2011-11-18 16:40:48 -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.