Martin Storsjö <mar...@martin.st> writes: > On Tue, 17 Dec 2013, Niels Möller wrote: > >> There's also IFUNC relocations, but I'm not sure which systems beyond >> vanilla gnu/linux support them. Are they usable on android, e.g.? > > Not sure - and even if they are they might not have been supported > from the beginning, so it might only be usable from some particular > android version. > > Can you provide some small example that I could try on a range of > versions?
No, sorry. I'm not very familier with IFUNC and have never used it myself. I just know it's a feature in glibc and ld.so. The basic idea, as far as I understand, is that you register a custom resolve function to a symbol. When ld.so tries to resolve that symbol, the registered function is called, and it returns the address of the real function, which ld.so then installs it the proper place (in the PLT array, I guess). Using it avoids one level of indirection, compared to using a wrapper function in Nettle which jumps through a function pointer. I also don't know if it works at all with static libraries. >> I'd expect pre-v6 arm to be used only in embedded systems where the >> cpu flavor is known at build time. > > ARMv5 is the baseline for the Android ARM ABI, which might be the main > reason why anybody would care. In practice I'm not sure if any such > devices actually have shipped - at least the first devices actually > were ARMv6. If in practice, ARMv5 isn't used, I think we can ignore this for now (and simply disable fat when nettle is configured for pre-v6 ARM). Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
