Searched refs:linker (Results 1 – 25 of 80) sorted by relevance
1234
96 if test -f $ROOT_OUT/system/etc/linker.config.json; then97 …conv_linker_config proto -s $ROOT_OUT/system/etc/linker.config.json -o $ROOT_OUT/system/etc/linker…114 if test -f $dst/etc/linker.config.json; then115 conv_linker_config proto -s $dst/etc/linker.config.json -o $dst/etc/linker.config.pb
5 Linkerconfig is a program to generate linker configuration based on the runtime16 ### linker.config.json19 creates linker configuration with the module. This module can be defined as23 A linker configuration file(linker.config.json) is compiled into a protobuf at build time24 by `conv_linker_config`. You can find the compiled file under `<base>/etc/linker.config.pb`.25 For example, `/apex/com.android.art/etc/linker.config.pb` is a configuration for the `com.android.a…28 `/system/etc/linker.config.pb`(or its source module `system_linker_config`) is special because33 linker.config.json file is in json format which can contain properties as below.67 [ld.config.format.md](https://android.googlesource.com/platform/bionic/+/master/linker/ld.config.fo…
44 TEST(linker, load_existing_lib) { in TEST() argument52 TEST(linker, load_nonexisting_lib) { in TEST() argument
2 # Please update linker configuration generator instead.
6 /bin/linker(64)? u:object_r:system_linker_exec:s0
11 srcs: ["linker.cpp"],
95 # dynamic linker when it re-executes /init to switch into the second stage.96 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed98 # domain (the source domain) to execute the dynamic linker (system_file type).102 # The label for the dynamic linker is rootfs in the recovery partition. This is because
44 # the dynamic linker and shared libraries.50 # linker tries to resolve paths in ld.config.txt.
100 # dynamic linker when it re-executes /init to switch into the second stage.101 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed103 # domain (the source domain) to execute the dynamic linker (system_file type).107 # The label for the dynamic linker is rootfs in the recovery partition. This is because
48 # the dynamic linker and shared libraries.54 # linker tries to resolve paths in ld.config.txt.
92 # dynamic linker when it re-executes /init to switch into the second stage.93 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed95 # domain (the source domain) to execute the dynamic linker (system_file type).99 # The label for the dynamic linker is rootfs in the recovery partition. This is because
38 src: "etc/linker.config.json",
97 // Core implementation, linked into libdebuggerd_handler and the dynamic linker.137 // Fallback implementation, for use in the Bionic linker only.140 visibility: ["//bionic/linker"],
33 All variant-specific compiler and linker flags are held under variables that36 linker flags are compatible with all toolchains. For example: if a target uses a91 specifically the compiler (`TARGET_CC`), archiver (`TARGET_AR`), and the linker92 (`TARGET_LD`). Architecture specific compiler and linker flags are passed in via
26 included in linker arguments when using lld.35 if it is being compiled with the llvm linker lld, it might be necessary36 to add the linker option `-Wl,-zseparate-code` to avoid creating an elf66 * Support for the linker read-only segment option (b/109657296).
66 # The dl.exec_linker* tests need to execute /system/bin/linker
73 # Allow to access the linker through the symlink.
88 map: start: e87b0000 end: e880d000 offset: 0 load_bias: 0 flags: 5 name: /system/bin/linker89 map: start: e880d000 end: e880f000 offset: 5c000 load_bias: 0 flags: 1 name: /system/bin/linker90 map: start: e880f000 end: e8810000 offset: 5e000 load_bias: 0 flags: 3 name: /system/bin/linker