Peter Smith

https://github.com/ARM-software/abi-aa/pull/267 to update wording.

I'm going to use the official terminology of `caller-save` instead of `callee_trash`. Just to be sure, apologies if this was already clear, `caller-save` and `callee-save` are more like responsibilities to...

OK I see where you are coming from. The safest assumption is that what is not callee-saved by the callee must be caller-saved. That would indeed imply that `p0~p15` would...

Thanks for the additional points. This has somewhat spiralled from the meaning of `it` :-) in a couple of sentences. I'll discuss with my colleagues to see if there is...

Looking at the table that you have updated I think it is best not to try and enumerate the caller-save registers and caller-save registers in the same table. The callee-save...

I've edited my * comment to "In practice this means all SVE state including predicate registers". Hopefully that should cover it.

Thanks for the detailed report. Apologies for the delay in responding, we're just coming back off vacation. It would be best to report this in upstream llvm-project. As a rule...

Would you be able to be more specific about what you found difficult? I'm not sure that there is much that can be usefully written in that section. The ABI...

As mentioned in https://github.com/ARM-software/abi-aa/pull/223 there is a generic ABI issue with how GDAT(S+A) is written vs how it is implemented https://github.com/ARM-software/abi-aa/issues/217 . No linker implements it as written, and the...

I've submitted https://github.com/ARM-software/abi-aa/pull/272 which removes A from the GDAT(S + A) relocation operation.