This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:multiasm:papc:chapter_6_4 [2025/05/18 18:43] – [Bit field data type] ktokarz | en:multiasm:papc:chapter_6_4 [2025/05/18 19:02] (current) – [Pointers] ktokarz | ||
|---|---|---|---|
| Line 96: | Line 96: | ||
| <figure bitfieldtype> | <figure bitfieldtype> | ||
| - | {{ : | + | {{ : |
| < | < | ||
| </ | </ | ||
| Line 102: | Line 102: | ||
| ===== Pointers ===== | ===== Pointers ===== | ||
| - | Pointers store the address of the memory which contains interesting information. They can point to the data or the instruction. If the segmentation is enabled, pointers can be near or far. The far pointer contains the logical address (formed with the segment and offset parts). The near pointer contains the offset only. The offset can be 16, 32 or 64 bits long. The segment selector is always stored as a 16-bit number. | + | Pointers store the address of the memory which contains interesting information. They can point to the data or the instruction. If the segmentation is enabled, pointers can be near or far. The far pointer contains the logical address (formed with the segment and offset parts). The near pointer contains the offset only. The offset can be 16, 32 or 64 bits long. The segment selector is always stored as a 16-bit number. |
| + | |||
| + | <figure pointertypes> | ||
| + | {{ : | ||
| + | < | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | The offset is often the result of complex addressing mode calculations and is called an effective address. | ||
| + | </ | ||