Home
last modified time | relevance | path

Searched refs:on (Results 1 – 25 of 49) sorted by relevance

12

/bionic/docs/
Ddefines.md11 the system property functions. Common alternatives on this dimension are
13 seen on Android devices, it is possible to use bionic on the host too.
18 useful as you might think, and one of the other choices on this page is usually
20 of the OS and needs to behave differently on the host than on the device.
22 remember that it is possible -- if unusual -- to use bionic on the host).
41 well on a desktop Linux distro, say. Common alternatives on this dimension
65 If your code depends on "bitness" -- whether `long` and pointers are 32- or
Dfdtrack.md8 that's invoked on file descriptor operations, and a library that implements a
32 don't use it in code that can be used on multiple platform versions.)
36 backtraces. Instead, if you can detect that an fd leak is ongoing, turning on
40 on fdtrack when it hits a threshold, and then aborts after another threshold.
49 * Primary method on the platform
62 * Requires -fno-omit-frame-pointer to be used on all code being unwound
63 through, which currently isn't the case on Android
64 * Frame layout is a mess on 32-bit ARM: the ARM standard, clang, and GCC
Dlibc_assembler.md16 When benchmarking, it's best to verify on the latest Pixel device supported.
18 there is no major difference in performance on each.
39 and pushed on to the device. The commands below show how to do this.
74 Bionic benchmarks is based on the [Google Benchmarks](https://github.com/google/benchmark)
77 Run on (8 X 1844 MHz CPU s)
97 out the cpu very quickly on Pixel devices, and don't affect the results.
119 on device. If you are trying to run this using adb directly from a host
130 When verifying an assembler routine that operates on buffer data (such as
156 verify that when registers are pushed on the stack that there is cfi
DNOTICE42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
Delf-tls.md21 At run-time, TLS variables are allocated on a module-by-module basis, where a module is a shared
25 few instructions. TLS variables belonging to dlopen'ed shared objects, on the other hand, may be
39 for Itanium. The choice has effects on the toolchain, loader, and libc. In particular, when linking
116 musl, on the other, preallocates TLS memory in `pthread_create` and in `dlopen`, and each can report
203 * Specifiers on the variable (`static`, `extern`, ELF visibility attributes).
222 omitted if the loader only allowed zero-initialized TLS segments and didn't reclaim memory on
324 * GCC and the BFD linker support both designs on all supported Android architectures (arm32, arm64,
326 * GCC can select the design at run-time using `-mtls-dialect=<dialect>` (`trad`-vs-`desc` on arm64,
328 * GCC and Clang default to TLSDESC on arm64 and the traditional design on other architectures.
365 can't link code using TLSDESC at all, except on arm64, where it's used by default.
[all …]
Dclang_fortify_anatomy.md15 getting up-to-speed on how things function can be quite difficult.
21 all implementations of FORTIFY rely heavily on C language extensions in order
47 since FORTIFY's design for both Clang and GCC relies on optimizations in order
49 analysis of FORTIFY functions and commentary on builtins assume that code is
52 ### A note on GCC
62 requires things like macros that expand to unbalanced braces depending on your
112 redundant information. Each one focuses on different aspects of FORTIFY.**
118 generated code depending on the value of `_FORTIFY_SOURCE`. Further, said
194 So let's walk through this step by step, to see how FORTIFY does what it says on
201 `if (...) { ... }` can be optimized out. Depending on how late this happens,
[all …]
Dfdsan.md12on double free. File descriptors, on the other hand, are mandated by the POSIX standard to be allo…
47 …if someone tries to close a file descriptor that they don't own, depending on configuration, eithe…
49 The way this is implemented is by providing functions to set a 64-bit closure tag on a file descrip…
188 ...in the obviously correct bystander? What's going on here?
347 // if available, and fall back to no-ops or regular close on pre-Q devices.
368 …leDescriptor` via Intent, and then passing it into JNI code that ends up calling close on it. <br/>
375 …e leading to SQLite database corruption](https://code.fb.com/ios/debugging-file-corruption-on-ios/)
Dnative_allocator.md2 This document describes how to verify the native memory allocator on Android.
11 to run in on Android. The first is the normal allocator, the second is
12 called the svelte config, which is designed to run on memory constrained
57 kernel on free calls. This is important in Android to avoid consuming extra
72 For all applications on Android, the call `mallopt(M_DECAY_TIME, 1)` is
130 allocator on Android. One is allocation speed in various different scenarios,
159 Which will lock the benchmark to only run on core XX. This also avoids
161 with different characteristics. For example, on a big-little cpu, if the
170 Choosing to run on the little core can tend to highlight any performance
255 calls, and they tend to be on the critical path of applications.
[all …]
D32-bit-abi.md6 that use `off_t` to working on files no larger than 2GiB.
84 ## `time_t` is 32-bit on LP32 (y2038)
92 but the kernel interfaces exposed on 32-bit Android all use the 32-bit
95 times to/from the kernel, but we do not plan on adding support for
105 This doesn't generally affect Android devices, because on devices
/bionic/libc/malloc_debug/
DREADME_marshmallow_and_earlier.md7 This documentation describes how to enable this feature on API level
9 functional until API level 19, so using it on a version older than that
12 The documentation for malloc debug on newer versions of Android is
17 run as root on the device.
90 the time of the free is recorded. As with the backtrace on allocation,
94 on the list is removed and verified that it still contains the pattern 0xef.
106 Do not use this option value, it only works on the emulator. It has not
109 Enable on Certain Processes
112 cause malloc debug to only be used on processes with that name. For example,
/bionic/tests/
Dmake_fortify_compile_test.mk5 $(LOCAL_PATH)/touch-obj-on-success
7 LOCAL_CXX := $(LOCAL_PATH)/touch-obj-on-success \
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
/bionic/
Dandroid-changes-for-ndk-developers.md45 on the dynamic linker's search path. This meant that apps
46 had to call `dlopen` or `System.loadLibrary` on all transitive
59 library and symbol lookup changes on all past (and future) Android versions.
86 on its search path.
104 feature >= Android M but still works on older releases.)
122 Some apps have bad DT_NEEDED entries (usually absolute paths on the build
124 but the basename. These apps will fail to load on API level 23 and above.
146 (on a 4096-byte boundary) in the zip file and stored uncompressed.
171 them more likely to fail on specific devices, or on future releases ---
204 *Resolution*: rewrite your native code to rely only on public API. As a
[all …]
DREADME.md10 # Working on bionic itself
43 Android, that's either `linker` or `linker64` (depending on whether it's a
82 # The public header files on everyone's include path. These are a mixture of
162 See SYSCALLS.TXT itself for documentation on the format.
165 on [man7.org](https://man7.org/linux/man-pages/dir_section_2.html).
187 use over the `void *` you'll see on man7.org.)
193 only a brief one-sentence explanation (usually based on the description
205 because they won't be on the man7.org page.
209 7. Add a basic test. Don't try to test everything; concentrate on just testing
224 For testing the *kernel* side of things, we should prefer to rely on
[all …]
/bionic/build/
DNOTICE42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
/bionic/apex/
DNOTICE42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
/bionic/tools/
DNOTICE10 distributed under the License is distributed on an "AS IS" BASIS,
26 distributed under the License is distributed on an "AS IS" BASIS,
/bionic/libdl/
DNOTICE10 distributed under the License is distributed on an "AS IS" BASIS,
26 distributed under the License is distributed on an "AS IS" BASIS,
DAndroid.bp64 // a) pull symbols from libgcc.a and b) depend on libdl.so will not rely on libdl.so
168 // a) pull symbols from libgcc.a and b) depend on libdl.so will not rely on libdl.so
/bionic/linker/
DAndroid.bp2 // linker_wrapper - Linux Bionic (on the host)
5 // This is used for bionic on (host) Linux to bootstrap our linker embedded into
132 // Enable a module on all targets the linker runs on (ordinary Android targets, Linux Bionic, and
349 // This line should be unnecessary because the linker's dependency on libunwind_llvm.a should
442 // a) pull symbols from libgcc.a and b) depend on ld-android.so will not rely on ld-android.so
/bionic/benchmarks/
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
DAndroid.bp11 // distributed under the License is distributed on an "AS IS" BASIS,
131 // Only supported on linux systems.
DNOTICE10 distributed under the License is distributed on an "AS IS" BASIS,
26 distributed under the License is distributed on an "AS IS" BASIS,
42 distributed under the License is distributed on an "AS IS" BASIS,
58 distributed under the License is distributed on an "AS IS" BASIS,
74 distributed under the License is distributed on an "AS IS" BASIS,
118 distributed under the License is distributed on an "AS IS" BASIS,
/bionic/libc/arch-x86_64/bionic/
Dsyscall.S45 # (Not all will be valid, depending on the syscall.)
/bionic/libc/arch-riscv64/bionic/
D__bionic_clone.S61 # Call __start_thread with the 'fn' and 'arg' we stored on the child stack.

12