2026-04-16 19:40 UTC
@bal4e @folkertdev
The problems with ifuncs this way is a few issues; first the resolver function has to be simple and not do anything else except load from memory and return a function.
Second is well it depends on glibc dynamic loader (I think the bonic loader now supports it; musl folks said they won't be). So it is not exactly portable.
LLVM/clang supports this functionality and extends it to be more "portable" instead it adds check for null on a location and calls the resolver and sets the location that way. I have not looked into the exact details there though.
Replies (1)
-
@folkertdev@hachyderm.io 2026-04-16 20:19
@pinskia @bal4e it would be neat if LLVM can paper over the differences. We'd need a portable and robust implementation of course. Though it's totally possible that we have a generic implementation and then a specialized one if the conditions are satisfied.