Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:multiasm:cs:chapter_3_10 [2026/03/01 14:13] – [Program control flow destination addressing] ktokarz | en:multiasm:cs:chapter_3_10 [2026/05/27 09:24] (current) – [Absolute and Relative addressing] ktokarz |
|---|
| </figure> | </figure> |
| |
| **Indirect addressing** of the destination uses the content of the register as the address where the program will jump. In the following example, the processor will jump to the destination address, which is stored in //R0//: | **Indirect addressing** of the destination, as shown in Fig {{ref>jumpindirect}} uses the content of the register as the address where the program will jump. In the following example, the processor will jump to the destination address, which is stored in //R0//: |
| <code> | <code> |
| jump [R0] | jump [R0] |
| |
| Absolute addressing is simple and doesn't require any additional calculations by the processor. It is often used in embedded systems, where the software is installed and configured by the designer, and the location of programs does not change. | Absolute addressing is simple and doesn't require any additional calculations by the processor. It is often used in embedded systems, where the software is installed and configured by the designer, and the location of programs does not change. |
| Absolute addressing is difficult to use in general-purpose operating systems like Linux or Windows, where users can start a variety of programs, and their placement in memory varies each time they're loaded and executed. Much more useful is the **relative addressing**, where operands are specified as differences from a memory location and some known value, which can be easily modified and accessed. Often, the operands are provided relative to the Instruction Pointer, which allows the program to be loaded at any address in the address space, but the distance between the currently executed instruction and the location of the data it wants to reach is always the same. This is the default addressing mode in the Windows operating system, working on x64 machines. It is illustrated in Fig{{ref>addrrelative}}. | Absolute addressing is difficult to use in general-purpose operating systems like Linux-based or Windows, where users can start a variety of programs, and their placement in memory varies each time they're loaded and executed. Much more useful is the **relative addressing**, where operands are specified as differences from a memory location and some known value, which can be easily modified and accessed. Often, the operands are provided relative to the Instruction Pointer, which allows the program to be loaded at any address in the address space, but the distance between the currently executed instruction and the location of the data it wants to reach is always the same. This is the default addressing mode in the Windows operating system, working on x64 machines. It is illustrated in Fig {{ref>addrrelative}}. |
| |
| <figure addrrelative> | <figure addrrelative> |
