aaelf64 is unclear about state of pauth relocations

[richlowe]

The document says that the pauth relocations will be added when pauth itself is out of alpha, but pauth is still in alpha and the relocations are also added.

should relocations with these names and values be included in software in general, or not?

[smithp35]

The document says that the pauth relocations will be added when pauth itself is out of alpha, but pauth is still in alpha and the relocations are also added.

That sounds like a sentence that I need to find and remove.

PAuthABI, the overall specification, is still in Alpha, in that it is following the implementation in upstream LLVM and that hasn't fully landed yet. However I don't expect any change to the relocation codes, and it was at the stage where it would be better to put them in the main AAELF so that codes are stable and are not inadvertantly reused. If I were to put a status on just the relocations I'd day Beta as I can't completely rule out a change if the sole implementation requests it. Again; not expecting any changes.

The PAuthABI is an extension to the ABI, which tools do not need to implement to be conformant with the base standard ABI. To make it work needs changes across a whole platform, including toolchain and OS. I would not expect to see these relocations to appear outside of that context.