Richard Earnshaw

I'm mostly a GCC for arm maintainer, but Will asked me if I could have a quick look at this. I'm generally not convinced that trying to pick an architecture...

Well that depends on the context of its use. If it's used as a verb then "trade off" is clearly correct. But if used as a noun then you're correct.

Whilst there is room for improvement in the wording here, I don't entirely agree with this change. Conceptually, at least (it may be different in environments where memory is flat-mapped...

Of course, there is also 'shared memory': memory that is shared by two or more processes. How such sharing is done is, I think, beyond the scope of the AAPCS...

> "May" is the correct term here. In standards documents like these it always has the specific meaning of "permitted but not required". Using another word or term would just...

Why does it need to be defined? It's just a hook for the linker to calculate offsets against. Indeed, on AArch32 there's the potential to put the __GLOBAL_OFFSET_TABLE__ in the...

I might be inclined to turn the initial part of your suggested change on its head. Perhaps something like `Semihosting is not designed to be used as a mechanism to...

The ABI has always used the principle of ‘dumb format, smart tools’. That means that whenever there is a choice to make, as here, we favour the form that allows...

> My alternative scheme solves the problem by inserting an ending $x at the previous section. I’m not sure that’s well defined. You would have a symbol that lies outside...

> If mapping symbols were allowed and recommended to have sizes, and a default symbol defined for each section type, then it would be possible to remove many symbols entirely,...