From 60f098f841198d06a3b10d66c99c4778f2167fbb Mon Sep 17 00:00:00 2001 From: Warner Losh Date: Sat, 13 Jul 2024 23:47:20 -0600 Subject: [PATCH] arch: Update to remove armv6 There were two stray places where armv6 remained that shouldn't be there. Remove them. Replace one with aarch64 and update MACHINE_ARCH description of amd64 while I'm here. Eliminate a near-by contraction igor noted. Sponsored by: Netflix --- share/man/man7/arch.7 | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/share/man/man7/arch.7 b/share/man/man7/arch.7 index 88228b807e6a..21d2b156af87 100644 --- a/share/man/man7/arch.7 +++ b/share/man/man7/arch.7 @@ -24,7 +24,7 @@ .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" -.Dd June 19, 2024 +.Dd July 13, 2024 .Dt ARCH 7 .Os .Sh NAME @@ -161,12 +161,11 @@ Examples are: .Pp .Dv aarch64 will support execution of -.Dv armv6 -or .Dv armv7 binaries if the CPU implements .Dv AArch32 -execution state, however older arm binaries aren't supported. +execution state, however older arm binaries are not supported by +.Fx . .Pp On all supported architectures: .Bl -column -offset -indent "long long" "Size" @@ -374,15 +373,19 @@ It, along with defines the ABI used by the system. Generally, the plain CPU name specifies the most common (or at least first) variant of the CPU. -This is why powerpc and powerpc64 imply 'big endian' while 'armv6' and 'armv7' +This is why powerpc and powerpc64 imply 'big endian' while armv7 and aarch64 imply little endian. If we ever were to support the so-called x32 ABI (using 32-bit pointers on the amd64 architecture), it would most likely be encoded as amd64-x32. -It is unfortunate that amd64 specifies the 64-bit evolution of the x86 -platform (it matches the 'first rule') as everybody else uses x86_64. -There is no standard name for the processor: each OS selects its own -conventions. +It is unfortunate that amd64 specifies the 64-bit evolution of the x86 platform +(it matches the 'first rule') as almost everybody else uses x86_64. +The +.Fx +port was so early, it predated processor name standardization after Intel joined +the market. +At the time, each OS selected its own conventions. +Backwards compatibility means it is not easy to change to the consensus name. .It Dv MACHINE_CPUARCH Represents the source location for a given .Dv MACHINE_ARCH .