--- wikisrc/ports/evbarm.mdwn	2018/11/22 00:56:36	1.58
+++ wikisrc/ports/evbarm.mdwn	2018/11/22 01:03:52	1.59
@@ -78,18 +78,21 @@ Note that these are all little endian, a
 with a "eb" sufix.   
 
 [[!table data="""
-MACHINE_ARCH | 32/64 | ARM architecture version | ABI
-arm | 32 | ? | oabi
-earm | 32 | armv4 (effectively an alias) | eabi
-earmv4 | 32 | armv4 (no thumb, so ok on strongarm) | eabi
-earmv5 | 32 | armv5t | eabi
-earmv6 | 32 | armv6 | eabi
-earmv7 | 32 | armv7 | eabi
-aarch64 | 64 | armv8 | \todo ? eabi
+MACHINE_ARCH |bits | ARM architecture version            |ABI
+arm          |32   |?                                    |oabi
+earm         |32   |armv4 (effectively an alias)         |eabi
+earmv4       |32   |armv4 (no thumb, so ok on strongarm) | eabi
+earmv5       |32   |armv5t                               |eabi
+earmv6       |32   |armv6                                |eabi
+earmv7       |32   |armv7                                |eabi
+aarch64      |64   |armv8                                |\todo ? eabi
 """]]
 
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.
 
+\todo Explain why aarch64 is a MACHINE_ARCH, when it seems like it
+should be something like armv8hf_64.
+
 \todo Explain if MACHINE_ARCH values correspond to a particular
 argument to some CPU selection command in gcc (and/or clang).