| Rev | Author | # | Line |
|---|---|---|---|
| 17 | LawrenceDoliveiro | 1 | Numbering of bits within a byte, and bytes within a multi-byte integer, to correspond more closely to the order in which one might read them in a memory dump. Opposite of LittleEndian. |
| 12 | JohnMcPherson | 2 | |
| 14 | AristotlePagaltzis | 3 | See [Endianness]. |
| 16 | AristotlePagaltzis | 4 | |
| 5 | ---- | ||
| 15 | LawrenceDoliveiro | 6 | |
| 7 | Odd fact: even on big-endian CPUs, registers are still little-endian. To see this, consider the following pseudo-AssemblyLanguage sequence: | ||
| 8 | |||
| 9 | * move two-byte integer from ''A'' to ''X'' | ||
| 10 | * move one-byte integer from ''X'' to ''B'' | ||
| 11 | |||
| 12 | Question: will the byte at ''B'' end up containing the high byte or the low byte of ''A''? | ||
| 13 | |||
| 14 | In little-endian architectures, the answer is always “the low byte”. However, in big-endian architectures, the answer depends on whether ''X'' is a memory location or a register; if it’s a memory location, then ''B'' gets the high byte. Otherwise, it gets the low byte. |
lib/blame.php:177: Warning: Invalid argument supplied for foreach()