platform_bionic/libc
David 'Digit' Turner 0dfd94cff4 am 4e57cf3f: Merge change 24463 into eclair
Merge commit '4e57cf3f8c0b696f117579c8165b13c8d32b9b5d' into eclair-plus-aosp

* commit '4e57cf3f8c0b696f117579c8165b13c8d32b9b5d':
  Fix an infinite loop in time2sub.
2009-09-09 18:01:11 -07:00
..
arch-arm Neon-optimized versions of memcpy. 2009-09-02 23:21:52 +02:00
arch-x86 Revert "Fix the C library initialization to avoid calling static C++ constructors twice." 2009-06-03 19:32:37 +02:00
bionic merge from open-source master 2009-09-01 08:27:42 -07:00
docs am cdb68bf8: Merge change 2470 into donut 2009-05-27 03:31:12 -07:00
include am 9e74f697: libc: add void to clock() function prototype 2009-09-09 15:13:56 -07:00
inet auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
kernel libc: kernel-headers: Add qdsp6 vdec header 2009-08-30 19:17:26 -07:00
netbsd Don't request IPv6 addresses if AI_ADDRCONFIG is specified and the system has no IPv6 connectivity. 2009-08-04 13:17:03 -07:00
private Pass the elfdata pointer in a slot of the temporary TLS area. 2009-07-17 17:55:01 +02:00
stdio auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
stdlib Fix __eabi_atexit() implementation, as well as a bug in the BSD-originated __cxa_finalize() implementation 2009-05-20 11:42:52 +02:00
string auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
tools auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
tzcode Fix an infinite loop in time2sub. 2009-09-09 17:45:00 -07:00
unistd auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
zoneinfo auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
Android.mk libc: Add an intermediate version of the static libc without malloc 2009-05-27 20:16:19 -07: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 auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
README Add an 's and a . to the bionic/libc README. 2009-07-23 17:41:47 -07:00
SYSCALLS.TXT auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -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.