Wilco1

I agree a summary description that explains how to use these relocations with an example would be great. Key things that would be useful to point out: - The checking...

Using prel on an absolute address is weird and non-intuitive. It would be more reasonable to do it like: ``` adrp x0, :pg_hi21_nc: global movk x0, :abs_g3: global add x0,...

Yes both relocation examples behave identically. You're right, the abs_g3 relocation is not allowed in shared objects, so using prel_g3 is the only option there. If we change prel_g3, it...

How could the registers after a context switch be in unprotected memory unless the OS is completely broken by design? If an attacker can read/write the stored registers of all...

Can we progress this? It seems there is agreement on most of these, so just keep FEAT_BTI.

A larger issue is that PLTs have become less efficient with the added BTI making them 20 bytes and span multiple fetch blocks. In principle we don't need BTI in...

What is the actual sequence to get the TLS pointer? If it's an indirection at a fixed offset from `TPIDR_EL0` then that could be emitted by compilers to avoid the...

Would it be feasible to use say `.lbss.nv_fatbin` and have the linker recognise the section as large based on the prefix? This was what I originally intended for the medium...

> As I understand it, marking a section SHF_*_LARGE flag on a section is not really a property of the section itself, but more an assertion/promise that all the sections...

I was thinking "any section > 1GB goes at the end" by default, but checking relocations would be even better. Then you could stop worrying about code models and just...