Hello !
Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
en:multiasm:cs:chapter_3_11 [2026/06/23 11:52] – [Endianness] ktokarzen:multiasm:cs:chapter_3_11 [2026/06/23 13:35] (current) – pczekalski
Line 3: Line 3:
  
 ===== Integers ===== ===== Integers =====
-Integer data types can be 8-, 16-, 32-, or 64-bit long. If the encoded number is unsigned, it is stored in binary, while if the value is signed, it is stored in two's complement. A natural binary number range starts with zero. In such a case, it contains all bits equal to zero. While it contains all bits equal to one, the value can be calculated with the expression\\ +Integer data types can be 8-, 16-, 32-, or 64-bit long. If the encoded number is unsigned, it is stored in binary; if it is signed, it is stored in two's complement. A natural binary number range starts with zero. In such a case, it contains all bits equal to zero. While it contains all bits equal to one, the value can be calculated with the expression\\ 
 {{:en:multiasm:cs:equation_binary.png?100 |}},\\ \\  {{:en:multiasm:cs:equation_binary.png?100 |}},\\ \\ 
 where n is the number of bits in a number.  where n is the number of bits in a number. 
Line 33: Line 33:
 <figure realtypes> <figure realtypes>
 {{ :en:multiasm:cs:floating_numbers.png?600 |Illustration of a single and double precision real numbers}} {{ :en:multiasm:cs:floating_numbers.png?600 |Illustration of a single and double precision real numbers}}
-<caption>Illustration of a single and double precision real numbers </caption>+<caption>Illustration of a Single and Double Precision Real Numbers</caption>
 </figure> </figure>
  
Line 65: Line 65:
 <figure littlebigendian> <figure littlebigendian>
 {{ :en:multiasm:cs:little_big_endian.png?600 |Illustration of Little and Big Endian data placement in the memory}} {{ :en:multiasm:cs:little_big_endian.png?600 |Illustration of Little and Big Endian data placement in the memory}}
-<caption>Illustration of Little and Big Endian data placement in the memory</caption>+<caption>Illustration of Little and Big Endian Data Placement in the Memory</caption>
 </figure> </figure>
  
 Big-endian is mainly used in network protocols, where the most significant bytes are sent first. In modern processors, the dominant data-placement order in memory is little-endian, although some processors (including ARM) can support both modes. Big endian is more human intuitive, but little endian makes it possible to access the same data with different sizes at the same address. It is important for fast data type casting (for example, treating a 32-bit integer as a 16-bit integer) because the starting address doesn't change. Some processors support conversion between little- and big-endianness with special instructions. Big-endian is mainly used in network protocols, where the most significant bytes are sent first. In modern processors, the dominant data-placement order in memory is little-endian, although some processors (including ARM) can support both modes. Big endian is more human intuitive, but little endian makes it possible to access the same data with different sizes at the same address. It is important for fast data type casting (for example, treating a 32-bit integer as a 16-bit integer) because the starting address doesn't change. Some processors support conversion between little- and big-endianness with special instructions.
en/multiasm/cs/chapter_3_11.txt · Last modified: by pczekalski
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0