Your agreement on the short / int / long / word / dword for the signed is not just x86-ism; this is windows-ism (SHORT / LONG / WORD / DWORD). I don’t understand why Windows programmers love them so much when the standard (u) int N _t types are more understandable for everyone.
I do not think x86 naturally comes with a "word" and a "double word"; the registers are al, ah (8 bits), ax (16 bits), eax (32-bits). I forgot how you indicated the size of the memory-memory move.
M68K instructions have .b (bytes),. W (word), and .l (long) suffixes. No double / quad-word IIRC.
ARM has ldb (byte), ldh (halfword), ldr (register).
The PPC has bytes, half-words, words, and the double word IIRC.
In general, it’s pretty pointless to talk about “word size” because it is highly architecture dependent, and even then it tends to change (I doubt that modern x86 implements 16-bit arithmetic faster than 32-bit arithmetic).
Then, pointer size determination is also defined, but amd64 has only 48-bit virtual addresses (the first 17 bits must be all 1 or all 0).
source share