Closed kovdan01 closed 2 months ago
Tagging @smithp35 Tagging @asl
I'm on vacation this week. Will get back to you after Easter.
It is most likely a typo, my memory is that I wanted to match the existing dynamic relocations. I'll check when I get back to see if there is any other reason.
I agree this is a typo. I've created https://github.com/ARM-software/abi-aa/pull/255 to fix.
To the best of my knowledge the Appendix on GOT generating relocations hasn't been implemented before. At the time of writing the interested parties preferred to have a RELRO unsigned GOT.
Closing the issue as resolved in #255
In https://github.com/ARM-software/abi-aa/blob/main/pauthabielf64/pauthabielf64.rst#auth-variant-got-generating-relocations, AUTH variants of GOT-generating relocations are defined. Their names are in most cases basically the same as corresponding non-AUTH relocs names, but for
R_AARCH64_AUTH_GOT_LO12_NC
, it's not true: the non-AUTH variant containsLD64
(R_<CLS>_LD64_GOT_LO12_NC
), so the AUTH variant should probably beR_AARCH64_AUTH_LD64_GOT_LO12_NC
. IfLD64
is considered redundant since we don't have 32-bit versions of AUTH relocations, it should be probably deleted from other AUTH relocs names: inR_AARCH64_AUTH_LD64_GOTOFF_LO15
andR_AARCH64_AUTH_LD64_GOTPAGE_LO15
,LD64
is present.Is
LD64
omitted inR_AARCH64_AUTH_GOT_LO12_NC
intentionally? If yes, it would be nice if you explain rationale of such decision.