Peter Smith
Peter Smith
Raised due to LLVM issue https://github.com/llvm/llvm-project/issues/63418 Raising this as an ABI issue rather than a two separate toolchain issues as it may be simpler to amend the ABI than try...
The PauthABI (https://github.com/ARM-software/abi-aa/blob/main/pauthabielf64/pauthabielf64.rst#10dynamic-section) and MemtagABI (https://github.com/ARM-software/abi-aa/blob/main/memtagabielf64/memtagabielf64.rst#6dynamic-section) documents have Dynamic Tags. It would be useful to reserve the values used in the main aaelf64.rst document, with forwarding descriptions to the appropriate...
The PAuthABI work that we have done in the ABI has been restricted to the ELF specification. In the 31-07-2023 PAuthABI sync-up the topic of DWARF support came up as...
Both clang and GCC leave out the `DW_AT_location` for TLS variables ostensibly due to lack of a relocation to describe the location in the debug data. For x86_64 `DW_AT_location` is...
With the tiny code model and a signed GOT, an adr instruction is needed to get the address of the GOT entry for input to the authenication. For example: adr...
As pointed out in https://github.com/ARM-software/abi-aa/issues/253 the R_AARCH64_AUTH_GOT_LO12_NC is meant to be the AUTH variant of R_AARCH64_LD64_GOT_LO12_NC. As there is also a R_AARCH64_LD32_GOT_LO12_NC relocation rename the relocation to R_AARCH64_LD64_AUTH_GOT_LO12_NC. These relocations...
There is a typo in the spelling of R_
The GDAT(S + A) relocation operation requires a static linker to create a GOT entry for (S + A). Requiring at least one GOT entry for each unique tuple (S,...
This has been raised from the discussion https://github.com/ARM-software/abi-aa/discussions/289 . Which I've quoted below The base ABI does not cover platform specific functions, it leaves the platform ABI to define these....
Add requirements for when a tool must generate a BTI instruction. This permits tools to elide BTI instructions when they can prove that no indirect branch to that location is...