diff options
| author | Scott Lobdell <slobdell@google.com> | 2019-08-25 12:20:54 -0700 |
|---|---|---|
| committer | Scott Lobdell <slobdell@google.com> | 2019-08-25 12:20:54 -0700 |
| commit | 4f9bfdcaca2414c8959986f0a4d73f16cb15e1c4 (patch) | |
| tree | 540bab5498d276cbbfad24c48a7ff989ee8b920a /docs/status.md | |
| parent | bfda022dd6fbbcea60e9f52496d90ece514b32da (diff) | |
| parent | f77cc9b224c35fa7d1d71e7c374ef19e47b5f6a5 (diff) | |
Merge RP1A.190822.001
Change-Id: Iaf90835a99d87f6246798efd2cea6fe9f750ea18
Diffstat (limited to 'docs/status.md')
| -rw-r--r-- | docs/status.md | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/docs/status.md b/docs/status.md index e1a5d349d..6968a1800 100644 --- a/docs/status.md +++ b/docs/status.md @@ -1,5 +1,11 @@ # Android bionic status +This document details libc/libm/libdl additions and behavior changes. + +See also +[Android linker changes for NDK developers](../android-changes-for-ndk-developers.md) +for changes related to native code loading in various Android releases. + ## Bionic function availability ### POSIX @@ -39,6 +45,9 @@ Current libc symbols: https://android.googlesource.com/platform/bionic/+/master/ New libc functions in R (API level 30): * Full C11 `<threads.h>` (available as inlines for older API levels). + * `memfd_create` and `mlock2` (GNU extensions). + * `renameat2` (GNU extension). + * `pthread_cond_clockwait`/`pthread_mutex_clocklock`/`pthread_rwlock_clockrdlock`/`pthread_rwlock_clockwrlock`/`sem_clockwait` New libc functions in Q (API level 29): * `timespec_get` (C11 `<time.h>` addition) @@ -301,7 +310,7 @@ targets N or later. The `_FORTIFY_SOURCE` macro can be used to enable extra automatic bounds checking for common libc functions. If a buffer overrun is detected, the program is safely aborted as in this -(example)[https://source.android.com/devices/tech/debug/native-crash#fortify]. +[example](https://source.android.com/devices/tech/debug/native-crash#fortify). Note that in recent releases Android's FORTIFY has been extended to cover other issues. It can now detect, for example, passing `O_CREAT` @@ -313,7 +322,7 @@ printf(3) family, or using the scanf(3) `m` modifier incorrectly will all result in FORTIFY failures even for code not built with FORTIFY. More background information is available in our -(FORTIFY in Android)[https://android-developers.googleblog.com/2017/04/fortify-in-android.html] +[FORTIFY in Android](https://android-developers.googleblog.com/2017/04/fortify-in-android.html) blog post. The Android platform is built with `-D_FORTIFY_SOURCE=2`, but NDK users |