bionic/libc
Nick Kralevich 6334c662ca Don't use -fstack-protector on ssp.c
libc's stack protector initialization routine (__guard_setup)
is in bionic/ssp.c. This code deliberately modifies the stack
canary.  This code should never be compiled with -fstack-protector-all
otherwise it will crash (mismatched canary value).

Force bionic/ssp.c to be compiled with -fno-stack-protector

Change-Id: Ib95a5736e4bafe1a460d6b4e522ca660b417d8d6
2012-07-10 10:51:41 -07:00
..
arch-arm arm: rewrite crtbegin* as C files. 2012-06-01 14:41:27 -07:00
arch-mips resolved conflicts for merge of e5408907 to jb-dev-plus-aosp 2012-05-09 13:53:37 -07:00
arch-sh/syscalls am 70cf0bc0: Merge "Remove the last references to SuperH." 2012-05-16 17:18:23 -07:00
arch-x86 arm: rewrite crtbegin* as C files. 2012-06-01 14:41:27 -07:00
bionic am 63c4179f: am 4d0128f1: Merge "Minor tweak to get memory around corrupted heap chunks dumped." into jb-dev 2012-06-19 11:33:19 -07:00
docs libc: Fix the definition of SIGRTMAX 2010-12-20 15:58:06 +01:00
include Merge "FORTIFY_SOURCE: Add openat, fix bug" 2012-07-09 12:55:32 -07:00
inet inet_ntop: pass the size of tmp to snprintf() 2012-06-11 16:00:52 -07:00
kernel Merge "Modify ion header" 2012-06-28 14:16:10 -07:00
netbsd am c5cab345: am 028ccf5d: Merge "Avoid multiple dns lookups for the same query" 2012-06-12 15:56:29 -07:00
private am c5cab345: am 028ccf5d: Merge "Avoid multiple dns lookups for the same query" 2012-06-12 15:56:29 -07:00
regex Remove compiler warnings when building Bionic. 2010-06-22 17:51:41 -07:00
stdio FORTIFY_SOURCE: add fgets support. 2012-07-09 09:57:18 -07:00
stdlib Enable functional DSO object destruction 2011-07-07 22:51:43 +02:00
string FORTIFY_SOURCE: add strlcpy / strlcat support 2012-06-14 12:52:42 -07:00
tools am 70cf0bc0: Merge "Remove the last references to SuperH." 2012-05-16 17:18:23 -07:00
tzcode libc: remove private declarations from <time.h> and <resolv.h> 2012-01-13 14:24:08 +01:00
unistd FORTIFY_SOURCE: Add openat, fix bug 2012-07-09 12:30:40 -07:00
wchar wchar.h: improve wchar_t support in Bionic 2010-06-15 07:04:41 -07:00
zoneinfo Update to tzdata2012c. 2012-04-02 07:43:15 -07:00
Android.mk Don't use -fstack-protector on ssp.c 2012-07-10 10:51:41 -07: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 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 resolved conflicts for merge of e5408907 to jb-dev-plus-aosp 2012-05-09 13:53:37 -07: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.