| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:multiasm:cs [2025/01/04 19:29] – ktokarz | en:multiasm:cs [2026/01/09 19:01] (current) – pczekalski |
|---|
| ====== Computer Architectures ====== | ====== Computer Architectures ====== |
| Assembler programming is a very low-level technique for writing the software. It uses the hardware directly relying on the architecture of the processor and computer with the possibility of having influence on every single element and every single bit in hundreds of registers which control the behaviour of the computer and all its units. That gives the programming engineer much more control over the hardware but also requires a high level of carefulness while writing programs. Modification of a single bit can completely change the way of a computer’s behaviour. | Assembler programming is a very low-level technique for writing software. It uses the hardware directly, relying on the processor's architecture and the computer's architecture, and can influence every element and every bit in hundreds of registers that control the computer's behaviour and all its units. That gives the programming engineer much more control over the hardware, but also requires careful attention when writing programs. A single-bit modification can completely change how a computer behaves. |
| This is why we begin our book on the assembler with a chapter about the architecture of computers. It is essential to understand how the computer is designed, how it operates, executes the programs, and performs calculations. It is worth mentioning that this is important not only for programming in assembler. The knowledge of computer and processor architecture is useful for everyone who writes the software in any language. Having this knowledge programming engineers can write more efficient applications in terms of memory use, time of execution and energy consumption. | This is why we begin our book on the assembler with a chapter on computer architecture. It is essential to understand how the computer is designed, how it operates, and how it executes programs and performs calculations. It is worth mentioning that this is important not only for programming in assembler. Knowledge of computer and processor architecture is useful to everyone who writes software in any language. With this knowledge, programming engineers can write more efficient applications in terms of memory use, execution time, and energy consumption. |
| |
| You can notice that in this book we often use the term processor for elements sometimes called in some other way. Historically the processor or microprocessor is the element that represents the central processing unit (CPU) only and requires also memory and peripherals to form the fully functional computer. If the integrated circuit contains all mentioned elements it is called a one-chip computer or microcontroller. A more advanced microcontroller for use in embedded systems is called an embedded processor. An embedded processor which contains other modules, for example, a wireless networking radio module is called a System on Chip (SoC). From the perspective of an assembler programmer differentiating between these elements is not so important, and in current literature, all such elements are often called the processor. That's why we decided to use the common name "processor" although other names can also appear in the text. | You can notice that in this book, we often use the term processor for elements that are sometimes called something else. Historically, the processor or microprocessor is the element that represents the central processing unit (CPU) only and requires memory and peripherals to form a fully functional computer. If the integrated circuit contains all the mentioned elements, it is called a one-chip computer or microcontroller. An embedded processor is a more advanced microcontroller used in embedded systems. An embedded processor that contains other modules, such as a wireless networking radio module, is called a System on Chip (SoC). From the perspective of an assembler programmer, differentiating among these elements is not particularly important, and in current literature, they are often collectively called the processor. That's why we decided to use the common name "processor", although other names can also appear in the text. |
| |
| | <WRAP excludefrompdf> |
| | More information is presented in the following chapters: |
| | * [[en:multiasm:cs:chapter_3_1]] |
| | * [[en:multiasm:cs:chapter_3_2]] |
| | * [[en:multiasm:cs:chapter_3_3]] |
| | * [[en:multiasm:cs:chapter_3_4]] |
| | * [[en:multiasm:cs:chapter_3_5]] |
| | * [[en:multiasm:cs:chapter_3_6]] |
| | * [[en:multiasm:cs:chapter_3_7]] |
| | * [[en:multiasm:cs:chapter_3_8]] |
| | * [[en:multiasm:cs:chapter_3_9]] |
| | * [[en:multiasm:cs:chapter_3_10]] |
| | * [[en:multiasm:cs:chapter_3_11]] |
| | * [[en:multiasm:cs:chapter_3_12]] |
| | * [[en:multiasm:cs:chapter_3_13]] |
| | </WRAP> |
