Searched refs:resolver (Results 1 – 6 of 6) sorted by relevance
87 ElfW(Addr) resolver = r->r_addend; in call_ifunc_resolvers()88 *offset = __bionic_call_ifunc_resolver(resolver); in call_ifunc_resolvers()108 ElfW(Addr) resolver = *offset; in call_ifunc_resolvers()109 *offset = __bionic_call_ifunc_resolver(resolver); in call_ifunc_resolvers()
30 extern "C" fn_ptr_t resolver() { in resolver() function
580 ElfW(Addr) resolver = r->r_addend + load_bias; in call_ifunc_resolvers()581 *offset = __bionic_call_ifunc_resolver(resolver); in call_ifunc_resolvers()590 ElfW(Addr) resolver = *offset + load_bias; in call_ifunc_resolvers()591 *offset = __bionic_call_ifunc_resolver(resolver); in call_ifunc_resolvers()
234 reference has a corresponding descriptor, which contains a resolver function address and an argument235 to pass to the resolver.250 long (*resolver)(long);257 return (char*)__get_tls() + desc.resolver(desc.arg);262 Static TLS Block, it can use a simple resolver function:272 To support modules loaded with `dlopen`, the loader must use a resolver function that calls282 * Unlike `__tls_get_addr`, the resolver function has a special calling convention that preserves285 * In general, the resolver function must call `__tls_get_addr`, so it must save and restore all287 * To keep the fast path fast, the resolver inlines the fast path of `__tls_get_addr`.288 * By storing the module's initial generation alongside the TlsIndex, the resolver function doesn't[all …]
97 # Contains the DNS resolver (originates from NetBSD code).
5651 ids to solve the resolver/named problem. But Niels designed the