From 7b26ede16e87394d04c6bf2e9efe465036f62120 Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Tue, 21 Jun 2022 12:23:26 -0400 Subject: [PATCH 1/6] Create endianness.md --- .../general/concepts/endianness/endianness.md | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 content/general/concepts/endianness/endianness.md diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md new file mode 100644 index 00000000000..c9f48873b83 --- /dev/null +++ b/content/general/concepts/endianness/endianness.md @@ -0,0 +1,37 @@ +--- +Title: 'Endianness' +Description: 'Endianness is a description of the order bytes are stored in memory for multi-byte values.' +Subjects: + - 'Computer Science' + - 'Code Foundations' +Tags: + - 'Numbers' + - 'Memory' +CatalogContent: + - 'paths/code-foundations' + - 'paths/computer-science' +--- + +Endianness is a description of the order bytes are stored in memory for multi-byte values. The options are generally described as big-endian or little-endian. A big-endian system stores the most significant byte at the smallest memory address and the least significant byte at the largest. A little-endian system stores the least significant byte at the smallest memory address and the most significant byte at the largest. + +## Example + +To store the 32-bit integer `0x0A0B0C0D` it is broken down into four bytes `0x0A`,`0x0B`,`0x0C`,`0x0D`. The endianness of the computer system defines in what order these bytes are stored in memory. The following examples show it stored at memory address `0xFFF0` for both big- and little-endian systems. +### Big-endian + +| Address | Value | +|---------|-------| +|`0xFFF0` |`0x0A` | +|`0xFFF1` |`0x0B` | +|`0xFFF2` |`0x0C` | +|`0xFFF3` |`0x0D` | + + +### Little-endian + +| Address | Value | +|---------|-------| +|`0xFFF0` |`0x0D` | +|`0xFFF1` |`0x0C` | +|`0xFFF2` |`0x0B` | +|`0xFFF3` |`0x0A` | From aadf229928975711c44a8564198c59b9caeef663 Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Tue, 21 Jun 2022 12:29:39 -0400 Subject: [PATCH 2/6] Update endianness.md --- .../general/concepts/endianness/endianness.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md index c9f48873b83..ba3f1454c3c 100644 --- a/content/general/concepts/endianness/endianness.md +++ b/content/general/concepts/endianness/endianness.md @@ -17,21 +17,21 @@ Endianness is a description of the order bytes are stored in memory for multi-by ## Example To store the 32-bit integer `0x0A0B0C0D` it is broken down into four bytes `0x0A`,`0x0B`,`0x0C`,`0x0D`. The endianness of the computer system defines in what order these bytes are stored in memory. The following examples show it stored at memory address `0xFFF0` for both big- and little-endian systems. -### Big-endian -| Address | Value | -|---------|-------| -|`0xFFF0` |`0x0A` | -|`0xFFF1` |`0x0B` | -|`0xFFF2` |`0x0C` | -|`0xFFF3` |`0x0D` | +### Big-endian +| Address | Value | +| -------- | ------ | +| `0xFFF0` | `0x0A` | +| `0xFFF1` | `0x0B` | +| `0xFFF2` | `0x0C` | +| `0xFFF3` | `0x0D` | ### Little-endian -| Address | Value | -|---------|-------| -|`0xFFF0` |`0x0D` | -|`0xFFF1` |`0x0C` | -|`0xFFF2` |`0x0B` | -|`0xFFF3` |`0x0A` | +| Address | Value | +| -------- | ------ | +| `0xFFF0` | `0x0D` | +| `0xFFF1` | `0x0C` | +| `0xFFF2` | `0x0B` | +| `0xFFF3` | `0x0A` | From c3c3a1523c0a282a7548b971b0eb0567e7d80a0a Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Sat, 25 Jun 2022 10:35:53 -0400 Subject: [PATCH 3/6] Update content/general/concepts/endianness/endianness.md Co-authored-by: Brandon Dusch --- content/general/concepts/endianness/endianness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md index ba3f1454c3c..45ad1448228 100644 --- a/content/general/concepts/endianness/endianness.md +++ b/content/general/concepts/endianness/endianness.md @@ -12,7 +12,7 @@ CatalogContent: - 'paths/computer-science' --- -Endianness is a description of the order bytes are stored in memory for multi-byte values. The options are generally described as big-endian or little-endian. A big-endian system stores the most significant byte at the smallest memory address and the least significant byte at the largest. A little-endian system stores the least significant byte at the smallest memory address and the most significant byte at the largest. +**Endianness** describes the order in which bytes are stored in memory for multi-byte values. The options are generally described as big-endian or little-endian. A big-endian system stores the most significant byte at the smallest memory address and the least significant byte at the largest. A little-endian system stores the least significant byte at the smallest memory address and the most significant byte at the largest. ## Example From 970a60640a158893906ae29075e1b60a250378a4 Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Sat, 25 Jun 2022 10:36:23 -0400 Subject: [PATCH 4/6] Update content/general/concepts/endianness/endianness.md Co-authored-by: Brandon Dusch --- content/general/concepts/endianness/endianness.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md index 45ad1448228..f329f70dca7 100644 --- a/content/general/concepts/endianness/endianness.md +++ b/content/general/concepts/endianness/endianness.md @@ -16,7 +16,14 @@ CatalogContent: ## Example -To store the 32-bit integer `0x0A0B0C0D` it is broken down into four bytes `0x0A`,`0x0B`,`0x0C`,`0x0D`. The endianness of the computer system defines in what order these bytes are stored in memory. The following examples show it stored at memory address `0xFFF0` for both big- and little-endian systems. +To store the 32-bit integer `0x0A0B0C0D` it is broken down into four bytes: + +- `0x0A` +- `0x0B` +- `0x0C` +- `0x0D` + +The endianness of the computer system defines in what order these bytes are stored in memory. The following examples show it stored at memory address `0xFFF0` for both big- and little-endian systems: ### Big-endian From 2f56ccd525f3e3aca125b3402db2cb20963c30bc Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Sat, 25 Jun 2022 10:36:30 -0400 Subject: [PATCH 5/6] Update content/general/concepts/endianness/endianness.md Co-authored-by: Brandon Dusch --- content/general/concepts/endianness/endianness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md index f329f70dca7..b388ca09ba6 100644 --- a/content/general/concepts/endianness/endianness.md +++ b/content/general/concepts/endianness/endianness.md @@ -1,6 +1,6 @@ --- Title: 'Endianness' -Description: 'Endianness is a description of the order bytes are stored in memory for multi-byte values.' +Description: 'Endianness describes the order in which bytes are stored in memory for multi-byte values.' Subjects: - 'Computer Science' - 'Code Foundations' From bfbe8069064b6316c19534f22f7abd4d6b74257c Mon Sep 17 00:00:00 2001 From: SSwiniarski <86081858+SSwiniarski@users.noreply.github.com> Date: Tue, 28 Jun 2022 16:59:47 -0400 Subject: [PATCH 6/6] Update content/general/concepts/endianness/endianness.md Co-authored-by: KTom101 --- content/general/concepts/endianness/endianness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/general/concepts/endianness/endianness.md b/content/general/concepts/endianness/endianness.md index b388ca09ba6..f9c9c0f0fc0 100644 --- a/content/general/concepts/endianness/endianness.md +++ b/content/general/concepts/endianness/endianness.md @@ -16,7 +16,7 @@ CatalogContent: ## Example -To store the 32-bit integer `0x0A0B0C0D` it is broken down into four bytes: +To store the 32-bit integer `0x0A0B0C0D`, it is broken down into four bytes: - `0x0A` - `0x0B`