Difference between revisions of "Endianness"

From Data Crystal
Jump to: navigation, search
m
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''Endianness''' or '''byte order''' is the order of [[Binary#Byte|bytes]] in a multi-[[Binary#Byte|byte]] value like a [[Binary#Word|word]]. Systems are ''usually'' referred to as either 'little endian', where the '''least significant byte''' (lsb) comes first, or 'big endian', where the '''most significant byte''' (msb) comes first.
+
'''Endianness''' or '''byte order''' is the order of [[Binary#Byte|bytes]] in a multi-[[Binary#Byte|byte]] value like a [[Binary#Word|word]]. Architectures may be "big", "little", or "bi-" endian.
  
The 6502 processor, used by the NES, expects addresses to be stored in 'little endian' order, with the least significant byte first and the most significant byte second.
+
In the context of romhacking, "endianness" is a misappropriation: its usage has nothing at all to do with the actual order of bytes its prefix denotes, but is rather the case of an error of articulation that became standardized, and so obtained a meaning independent of the conventions of language. In romhacking (as internally with respect to the CPUs used in older systems, "little-endian" means the least signficiant byte is ordered first in memory, not last. "Big-endian", conversely, means the most significant byte is first. "Little-endian" is actually "little-firstian" or "little-startian", and "Big-endian" is actually "Big-firstian" or "Big-startian" (only in the context of hacking).
  
{{moreinfo wikipedia|page=Endianness}}
+
Assemblers and compilers require the use of standard hexidecimal in code, which is little-endian in its truest sense, so the order in which you write the hex nibbles in your code may or may not be the order in which you pull them from memory, depending on the endianness of the architecture. (for example, it's not reversed on Sega Genesis, but is reversed on Nintendo or the Master System/Game Gear, for that matter).
 +
 
 +
Many newer architectures use bi-endianness, in which the endianess varies depending on the context.
 +
 
 +
==Little endian systems==
 +
* [[Nintendo Entertainment System]]
 +
* [[Super Nintendo]]
 +
* [[Nintendo Game Boy]]
 +
* [[Nintendo Game Boy Advance]]
 +
* [[Nintendo DS]]
 +
* [[Windows]]
 +
 
 +
==Big endian systems==
 +
* [[Sega Genesis]]
 +
* Many Internet protocols, such as TCP.
 +
 
 +
== See also ==
 +
 
 +
[https://en.wikipedia.org/wiki/Endianness Wikipedia article on endianness]
  
 
{{stub}}
 
{{stub}}

Latest revision as of 16:16, 6 April 2016

Endianness or byte order is the order of bytes in a multi-byte value like a word. Architectures may be "big", "little", or "bi-" endian.

In the context of romhacking, "endianness" is a misappropriation: its usage has nothing at all to do with the actual order of bytes its prefix denotes, but is rather the case of an error of articulation that became standardized, and so obtained a meaning independent of the conventions of language. In romhacking (as internally with respect to the CPUs used in older systems, "little-endian" means the least signficiant byte is ordered first in memory, not last. "Big-endian", conversely, means the most significant byte is first. "Little-endian" is actually "little-firstian" or "little-startian", and "Big-endian" is actually "Big-firstian" or "Big-startian" (only in the context of hacking).

Assemblers and compilers require the use of standard hexidecimal in code, which is little-endian in its truest sense, so the order in which you write the hex nibbles in your code may or may not be the order in which you pull them from memory, depending on the endianness of the architecture. (for example, it's not reversed on Sega Genesis, but is reversed on Nintendo or the Master System/Game Gear, for that matter).

Many newer architectures use bi-endianness, in which the endianess varies depending on the context.

Little endian systems

Big endian systems

See also

Wikipedia article on endianness