Lines Matching refs:in

7 for changes related to native code loading in various Android releases.
13 You can see the current status with respect to POSIX in the form of tests:
46 Run `./libc/tools/check-symbols-glibc.py` in bionic/ for the current
53 New libc functions in R (API level 30):
59 New libc behavior in R (API level 30):
63 New libc functions in Q (API level 29):
65   * `reallocarray` (BSD/GNU extension in `<malloc.h>` and `<stdlib.h>`)
66   * `res_randomid` (in `<resolv.h>`)
68   * `getloadavg` (BSD/GNU extension in <stdlib.h>)
70 New libc behavior in Q (API level 29):
72     special-case hack in `syslog`.
80   * Support in strptime for `%F`, `%G`, `%g`, `%P`, `%u`, `%V`, and `%v`.
84 New libc functions in P (API level 28):
102 New libc behavior in P (API level 28):
103   * `%C` and `%S` support in the printf family (previously only the wprintf family supported these).
104   * `%mc`/`%ms`/`%m[` support in the scanf family.
105   * `%s` support in strptime (strftime already supported it).
111 New libc functions in O (API level 26):
134 New libc behavior in O (API level 26):
139 New libc functions in N (API level 24):
141 …* all remaining `_FILE_OFFSET_BITS=64` functions, completing `_FILE_OFFSET_BITS=64` support in bio…
151 New libc behavior in N (API level 24):
154 New libc functions in M (API level 23):
172 New libc functions in L (API level 21):
203 New libc functions in K (API level 19):
211 New libc functions in J-MR2 (API level 18):
216 New libc functions in J-MR1 (API level 17):
221 New libc functions in J (API level 16):
243 ndk-r21$ for i in `ls -1v platforms/android-*/arch-arm/usr/lib/libc.so` ; do \
253 New libm functions in O (API level 26):
256 New libm functions in M (API level 23):
260 New libm functions in L (API level 21):
264 New libm functions in J-MR2 (API level 18):
272 but there are likely to be more in future because of Project Treble.
277 and in an attempt to flush out racy code, we changed how an invalid
287 in the caller, given that callers actually need the tid to pass to some
288 syscall or other, and sometimes update fields in the `pthread_internal_t`
303     rather than calling detach in the parent.
322 signal. This wasn't historically true in Android, and when we fixed this
332 overrun is detected, the program is safely aborted as in this
335 Note that in recent releases Android's FORTIFY has been extended to
342 all result in FORTIFY failures even for code not built with FORTIFY.
344 More background information is available in our
345 [FORTIFY in Android](https://android-developers.googleblog.com/2017/04/fortify-in-android.html)
349 need to manually enable FORTIFY by setting that themselves in whatever