Peter Smith

After discussion internally, we think it is best to keep with the existing text. The original text is written that way so that a linker can combine sections without needing...

Thanks very much for the report. We are aware of the CMake option and we are planning to investigate at a future point in time. From a glance at the...

Some additional thoughts on how we might be able to have a single newlib overlay package. If we can end up with a directory layout like ``` aarch64-none-elf |- aarch64a...

> > Do we really need to support .note.AARCH64-PAUTH-ABI-tag `NT_ARM_TYPE_PAUTH_ABI_TAG`? > > @MaskRay The spec has it defined, and I suppose there is a reason for this. We do not...

> > To the best of my knowledge I'm not aware of any of these as this is the only serious implementation of the ELF spec. > > I'm not...

These map on to different compiler command line-options. I would expect `armv8.1m.main_hard_fpdp_nomve` to be the best choice unless you know your programs are integer only. We don't currently build an...

I think we've got two possibilities. Add special cases (like in the 32-bit ABI) for ADRP, MOV (wide immediate), MOVZ and MOVK instructions. I see that in the 32-bit ABI...

Created https://github.com/ARM-software/abi-aa/pull/322 for bare-metal veneers

Thanks for raising. I've only skimmed through the proposals on the LLVM Discourse at the moment, will need to read it through in more detail to make sure I understand...

> A use case that springs to mind is controlling which thread pointer register a multithreaded libc uses, without having to either recompile it from source or indirect all TP...