Searched refs:general (Results 1 – 7 of 7) sorted by relevance
| /bionic/tests/ |
| D | elftls_test.cpp | 87 TEST(elftls, general) { in TEST() argument
|
| /bionic/libc/malloc_hooks/ |
| D | Android.bp | 90 test_suites: ["general-tests"],
|
| /bionic/libc/malloc_debug/ |
| D | Android.bp | 201 test_suites: ["general-tests"],
|
| /bionic/ |
| D | android-changes-for-ndk-developers.md | 6 See also [bionic status](docs/status.md) for general libc/libm/libdl
21 Our general practice with dynamic linker behavior changes is that they
|
| D | README.md | 267 A general example of adding a system call:
|
| /bionic/docs/ |
| D | clang_fortify_anatomy.md | 35 increasingly strict versions of it. In general, FORTIFY doesn't require user
110 **In general, when reading the below, be prepared for exceptions, subtlety, and
|
| D | elf-tls.md | 220 In general, supporting surplus TLS memory probably requires maintaining a thread list so that
285 * In general, the resolver function must call `__tls_get_addr`, so it must save and restore all
|