[PATCH 1/8] ld: Rename aarch64pe emulation target to arm64pe
Mark Harmstone
mark@harmstone.com
Wed Jan 4 02:38:54 GMT 2023
On 3/1/23 20:05, Martin Storsjö wrote:
> On Tue, 3 Jan 2023, Tamar Christina wrote:
>
>> I don't think we'll need to patch LLVM as you typically don't specify the emulation when using ld.
>
> When cross compiling, then the compiler driver (gcc or clang) will specify it.
I'm not 100%, but I'm fairly sure that GCC *always* passes the emulation name to ld.
> On Tue, 3 Jan 2023, Tamar Christina wrote:
>
> The reason for insisting on this change is non-technical in nature. For a project such as binutils we always want the primary name to reflect what the architecture calls things.
Which, while valid, is obviously not important enough to warrant adding unneeded complexity. And ARM Ltd. has at the very least acquiesced in the naming of the architecture as ARM64: see https://developer.arm.com/documentation/102474/0100/Fundamentals-of-Armv8-Neon-technology, "GNU and Linux documentation sometimes refers to AArch64 as ARM64". Or Microsoft's "PE Format" page, which is an official part of the UEFI specification, which uses "ARM64" throughout. And that's before we get to the fact that the corresponding "aarch32" seems to be used hardly anywhere.
It's also worth pointing out that there's no concept of emulation aliases at the moment, so someone would have to develop and test that. And having 300+ emulations, and an alias for just one, seems a little perverse.
Nick, what do you want me to do here?
Mark
More information about the Binutils
mailing list