Searched refs:linker (Results 1 – 18 of 18) sorted by relevance
/bionic/linker/ |
D | Android.bp | 5 // This is used for bionic on (host) Linux to bootstrap our linker embedded into 9 // embedded as the entry point, and the linker is embedded as ELF sections in 10 // each binary. There's a linker script that sets all of that up (generated by 51 // We need to access Bionic private headers in the linker. 56 // linker default configuration 59 // Configuration for the linker binary and any of its static libraries. 110 // We need to access Bionic private headers in the linker. 115 // linker components 118 // Enable a module on all targets the linker runs on (ordinary Android targets, Linux Bionic, and 149 // template for the linker binary [all …]
|
D | ld.config.format.md | 4 linker-namespace setup for dynamic executables. 10 2. Sections - contains linker-namespace configuration 35 # When this flag is set to true linker will set target_sdk_version for this binary to
|
D | ldd | 16 linker --list "$1"
|
/bionic/benchmarks/linker_relocation/ |
D | run_bench_with_ninja.sh | 40 --linker LINKER Run the benchmark using a specific dynamic linker 116 work_dir=$tmp_dir/linker-reloc-bench 122 target_dir=/data/local/tmp/linker-reloc-bench 124 (cd $tmp_dir; tar -c linker-reloc-bench/linker_reloc_bench_main linker-reloc-bench/*.so \ 133 if [ "$linker" != "" ]; then 134 main_cmd+=( $linker )
|
D | README.md | 3 This benchmark measures the time spent in the dynamic linker to load a large set 9 To run the benchmark, build the `linker-reloc-bench` target, sync `data`, and 10 run the benchmark from `/data/benchmarktest[64]/linker-reloc-bench`. 14 experimentation. The `--cc` and `--linker` flags allow swapping out different
|
D | Android.bp | 41 name: "linker-reloc-bench", 78 relative_install_path: "linker-reloc-bench",
|
/bionic/ |
D | android-changes-for-ndk-developers.md | 1 # Android linker changes for NDK developers 19 Our general practice with dynamic linker behavior changes is that they 31 * On a developer preview build, dynamic linker warnings will also show up 40 on the dynamic linker's search path. This meant that apps 44 dynamic linker's caching code cached failures too, so it was necessary 66 linker divides other libraries into the global group and the local 71 libraries. The M dynamic linker searches the global group followed by 80 `libfoo.so` instead, letting the dynamic linker find the correct library 97 symbol lookup and is now supported by the dynamic linker in API 23 and 104 The dynamic linker now understands the difference [all …]
|
D | OWNERS | 11 # Still the best reviewer for changes related to the dynamic linker.
|
D | README.md | 4 C library, math library, and dynamic linker. 28 The dynamic linker interface library. This is actually just a bunch of stubs 29 that the dynamic linker replaces with pointers to its own implementation at 39 #### linker/ --- /system/bin/linker and /system/bin/linker64 41 The dynamic linker. When you run a dynamically-linked executable, its ELF file 43 Android, that's either `linker` or `linker64` (depending on whether it's a
|
/bionic/apex/ |
D | Android.bp | 33 "linker", 72 "linker",
|
/bionic/docs/ |
D | elf-tls.md | 13 compiler, linker, dynamic loader, and libc. 40 an executable, the linker needs to know where an executable's TLS segment is relative to the TP so 320 The static linker can still relax a TLSDESC-based access to an IE/LE access. 324 * GCC and the BFD linker support both designs on all supported Android architectures (arm32, arm64, 333 The (static) linker frequently has more information about the location of a referenced TLS variable 335 object file compiled with `-fpic` is linked into an executable, the linker could relax GD accesses 336 to IE or LE. To relax a TLS access, the linker looks for an expected sequences of instructions and 487 …ation]: https://android.googlesource.com/platform/bionic/+/android-8.1.0_r48/linker/linker.cpp#2852 489 …nored]: https://android.googlesource.com/platform/bionic/+/android-8.1.0_r48/linker/linker.cpp#2784 508 `__libc_shared_globals` variable (see `tls_modules()` in [linker_tls.cpp][tls_modules-linker] and [all …]
|
D | 32-bit-abi.md | 35 [linker map](libc/libc.map.txt) for full details. Note also that in NDK r16 and
|
D | status.md | 6 [Android linker changes for NDK developers](../android-changes-for-ndk-developers.md)
|
/bionic/tests/libs/ |
D | segment_gap_outer.lds | 14 # Now create the gap. We need a text segment first to prevent the linker from
|
D | Android.bp | 306 // Build test helper libraries for linker namespaces 308 // This set of libraries is used to verify linker namespaces. 368 // Build test helper libraries for linker namespaces for allow all shared libs 370 // This set of libraries is used to verify linker namespaces for allow all 420 // Build test helper libraries for linker namespaces 460 // ns_hidden_child linker namespace test
|
/bionic/libdl/ |
D | Android.bp | 108 // provided by the linker. 187 // provided by the linker.
|
/bionic/tests/ |
D | Android.bp | 677 // Library of all tests (excluding the dynamic linker tests).
|
/bionic/libc/ |
D | Android.bp | 152 // compiled with -fno-stack-protector, since it accesses the stack canary TLS slot. In the linker, 196 // from the linker before ifunc resolvers have made string.h functions available. 1522 // This is a version of the static C library used by the dynamic linker that exclude malloc. It also
|