--- wikisrc/ports/evbarm.mdwn 2019/06/02 13:32:38 1.71 +++ wikisrc/ports/evbarm.mdwn 2019/06/12 08:29:41 1.72 @@ -51,52 +51,6 @@ set and the aarch64 architecture, built (Note also that armv8 is the first architecture to support aarch64, so this will not be an issue until at least armv9.) -#### ABI types - -There are two basic ABIs on ARM. One, called oabi, assumed a -particular kind of hardware floating point (FPA). This results in -faulting any floating-point instructions for kernel emulation on a -vast number of CPus, which is very slow. A newer one, called eabi, -has two variants. Both have stricter alignment rules, tending to 8 -byte rather than 4 bytes for 8-byte types (but actually read the specs -if you care). The one without "hf" emulates floating point without -causing traps/emulation, and "hf" uses VFP instructions, which are -present on modern CPUs. See the -[TS-7200](https://wiki.embeddedarm.com/wiki/EABI_vs_OABI) and -[Debian](https://wiki.debian.org/ArmEabiPort) documentation. - -Now, EABI is normal, and OABI is crufty. The only real reason NetBSD -retains OABI support is binary compatibility with older releases. The -"arm" and "armeb" MACHINE_ARCH targets are OABI; the rest of the -targets, all having "earm" are EABI. - -\todo CHECK THIS: The "aarch64" MACHINE_ARCH target is an EABI variant. - -### Relationship of MACHINE_ARCH to official ARM terminology - -Note that these are all little endian, and have big endian variants -with a "eb" suffix. Unless otherwise noted, all use the A32 or -aarch32 instruction set. - -[[!table data=<