Differences

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

Link to this comparison view

--- en:multiasm:cs:chapter_3_10 [2026/03/01 14:08] – ktokarz
+++ en:multiasm:cs:chapter_3_10 [2026/03/01 14:14] (current) – [Program control flow destination addressing] ktokarz
@@ Line 50: / Line 50: @@
 </figure>
-**Variations of indirect addressing**. The indirect addressing mode can have many variations in which the final address need not be the contents of a single register; it can be the sum of a constant and one or more registers. Some variants implement automatic incrementation (similar to the "++" operator) or decrementation ("- -") of the index register before or after instruction execution to make processing the tables faster. For example, accessing elements of the table where the base address of the table is named //data_table// and the register //R0// holds the index of the byte which we want to copy from a table to //R1// could look like this:
+**Variations of indirect addressing**. The indirect addressing mode can have many variations in which the final address need not be the contents of a single register; it can be the sum of a constant and one or more registers. Some variants implement automatic incrementation (similar to the "++" operator) or decrementation ("- -") of the index register before or after instruction execution to speed up processing of tables. For example, accessing elements of the table where the base address of the table is named //data_table// and the register //R0// holds the index of the byte which we want to copy from a table to //R1// could look like in Fig {{ref>addrindex}}, and in the code example:
 <code>
  copy R1, table[R0]
@@ Line 78: / Line 78: @@
 The operand of jump, branch, or function call instructions addresses the destination of the program flow control. The result of these instructions is the change of the Instruction Pointer content. Jump instructions should be avoided in high-level structural or object-oriented languages, but they are common in assembler programming. Our examples will use the hypothetic //jump// instruction with a single operand—the destination address.
-**Direct addressing** of the destination is similar to direct data addressing. It specifies the destination address as the constant value, usually represented by a name. In assembler, we define the names of the addresses in code as //labels//. In the following example, the code will jump to the label named //destin//:
+**Direct addressing** of the destination is similar to direct data addressing. It specifies the destination address as the constant value, usually represented by a name. In assembler, we define the names of the addresses in code as //labels//. In the following example, shown in Fig {{ref>jumpdirect}} and in the code, the program will jump to the label named //destin//:
 <code>
  jump destin
@@ Line 88: / Line 88: @@
 </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>
  jump [R0]

en/multiasm/cs/chapter_3_10.1772366927.txt.gz · Last modified: 2026/03/01 14:08 by ktokarz