You really need to lay this out differently, many CPUs have 2 different instruction set and ABIs for 32 vs 64 bit code. They also often have an intermediate 32bit ABI with 64bit instructions inside functions (sparc/PA-RISC/IA-64).
For x86 you have 16, 32 and 64bit versions,
PowerPC has 32 and 64,
ARM has 32 and thumb,
MIPS 32, 64 and mips16,
Sparc has v8, v8+ and v9,
PA-RISC has 1.1, 2.0 and 2.0W,
IA-64, HP-UX has a 32bit pointer ABI as well as 64bit.
I could also add a few DSP's and RISC embedded systems, but I'll stick to the main CPUs
plenty. I think you should count embedded chips because those are the only ones where it's still justified. (As in 2 K of code space or something) I wrote a IA32e operating system. http://www.losethos.com but I used as little assembly as possible. I wrote a compiler and assembler. Those are one of the few justifications to learn assembly.
6 comments
[ 3.2 ms ] story [ 19.7 ms ] threadFor x86 you have 16, 32 and 64bit versions,
PowerPC has 32 and 64,
ARM has 32 and thumb,
MIPS 32, 64 and mips16,
Sparc has v8, v8+ and v9,
PA-RISC has 1.1, 2.0 and 2.0W,
IA-64, HP-UX has a 32bit pointer ABI as well as 64bit.
I could also add a few DSP's and RISC embedded systems, but I'll stick to the main CPUs