Difference between revisions of "WhatsWrongWithO32N32N64"
From LinuxMIPS
| Line 5: | Line 5: | ||
Corporation and SGI: | Corporation and SGI: | ||
| − | * o32 is for 32-bit CPUs, or 64-bit CPUs running only a 32-bit subset | + | * o32 is for 32-bit CPUs, or 64-bit CPUs running only a 32-bit subset of the instruction set. |
| − | of the instruction set. | + | |
| − | * n32/n64 are for 64-bit CPUs only. n64 has 64-bit pointers and | + | * n32/n64 are for 64-bit CPUs only. n64 has 64-bit pointers and long integers, whereas n32 has 32-bit pointers and long integers. (Other than that they're pretty much the same and will be considered together). |
| − | long integers, whereas n32 has 32-bit pointers and long integers. | + | |
| − | (Other than that they're pretty much the same and will be considered | + | |
| − | together). | + | |
o32 is fairly different from n32/n64, so let's take them separately. | o32 is fairly different from n32/n64, so let's take them separately. | ||
Revision as of 12:49, 28 September 2005
What's wrong with o32, n32 and n64?
Linux/MIPS (up to now, Autumn 2005) has made progress using recognisable dialects of standards defined originally by MIPS Corporation and SGI:
- o32 is for 32-bit CPUs, or 64-bit CPUs running only a 32-bit subset of the instruction set.
- n32/n64 are for 64-bit CPUs only. n64 has 64-bit pointers and long integers, whereas n32 has 32-bit pointers and long integers. (Other than that they're pretty much the same and will be considered together).
o32 is fairly different from n32/n64, so let's take them separately.
