Lines Matching full:relocations

233 ## Text Relocations (Enforced for API level >= 23)
236 relocations. Such an approach reduces load time and improves security. This was
237 only a change for 32-bit, because 64-bit never supported text relocations.
239 The usual reason for text relocations was non-position independent
254 the TEXTREL entry declares that the .so contains text relocations.) This
264 entry/flag but without any actual text relocations. This doesn't happen
266 you're not generating ELF files that claim to have text relocations,
269 *Potential problems*: Relocations enforce code pages being writable, and
271 linker issued warnings about text relocations from API level 19, but on API
272 level 23 and above refuses to load code with text relocations.
275 no text relocations are necessary. The
277 has instructions for fixing text relocations, and more detailed
471 with IFUNC relocations. The affected functions are from `<string.h>`, but
475 ## Relative relocations (RELR)
477 Android added experimental support for RELR relative relocations
484 The RELR encoding is unrelated to the earlier "packed relocations"
489 relocations.
491 Prior to API level 35, there was a bug that caused RELR relocations to
492 be applied after packed relocations. This meant that ifunc resolvers
493 referenced by `R_*_IRELATIVE` relocations in the packed relocation
494 section would have been able to read globals with RELR relocations
497 should make sure not to store `R_*_IRELATIVE` relocations in packed
501 You can read more about relative relocations
503 https://maskray.me/blog/2021-10-31-relative-relocations-and-relr.