This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:multiasm:cs:chapter_3_11 [2026/06/23 11:50] – [Floating point] ktokarz | en:multiasm:cs:chapter_3_11 [2026/06/23 11:52] (current) – [Endianness] ktokarz | ||
|---|---|---|---|
| Line 58: | Line 58: | ||
| ===== Endianness ===== | ===== Endianness ===== | ||
| Data encoded in memory must be compatible with the processor. Memory chips are usually organised as a sequence of bytes, which means that every byte can be individually addressed. For processors with a class higher than 8-bit, there appears to be an issue with byte order in larger data types. There are two possibilities: | Data encoded in memory must be compatible with the processor. Memory chips are usually organised as a sequence of bytes, which means that every byte can be individually addressed. For processors with a class higher than 8-bit, there appears to be an issue with byte order in larger data types. There are two possibilities: | ||
| - | - Little | + | - Little |
| - | - Big Endian | + | - Big endian |
| These two methods for a 32-bit class processor are shown in Fig{{ref> | These two methods for a 32-bit class processor are shown in Fig{{ref> | ||