| Next revision | Previous revision |
| spo600:machine_language [2024/01/12 19:54] – created chris | spo600:machine_language [2025/01/08 21:44] (current) – chris |
|---|
| ====== Machine Language ====== | ====== Machine Language ====== |
| |
| //Machine language//, //machine code//, or //object code// is code that is directly executable by a CPU. It consist of a sequence of binary instructions encoded in a machine's [[Instruction Set Architecture]] (ISA) and is therefore very [[Portable|specific]] to a particular [[Computer Architecture|architecture]]. | //Machine language//, //machine code//, or //object code// is code that is directly executable by a CPU. It consist of a sequence of binary instructions encoded for a machine's [[Instruction Set Architecture]] (ISA) and is therefore very [[Portable|specific]] to a particular [[Computer Architecture|architecture]]. |
| |
| ===== General Format ===== | ===== General Format ===== |
| Machine code consists of a series of instructions, each of which specifies an operation and zero or more arguments. Each argument may indicate a [[register]], a [[Address|memory address]], or an [[Immediate Value|immediate value]]. | Machine code consists of a series of instructions, each of which specifies an operation and zero or more arguments. Each argument may indicate a [[register]], a [[Address|memory address]], or an [[Immediate Value|immediate value]]. |
| |
| Many early computers encoded the [[Operation|operation]] and [[Addressing Mode|addressing mode]] as a distinct [[Byte|byte]] or [[Word|word]] called an [[OpCode|opcode]], followed by zero or more additional bytes for the arguments, where the number of additional bytes is implied by the opcode. | Many early computers encoded the [[Operation|operation]] and [[Addressing Mode|addressing mode]] as a distinct [[word#byte|byte]] or [[Word|word]] called an [[OpCode|opcode]], followed by zero or more additional bytes for the arguments, where the number of additional bytes is implied by the opcode. |
| |
| Other processors encode instructions as bit values packed with a instruction field. For example, specific bits within an instruction word specify the operation, other bits specify the addressing mode, and still other bits specify the register(s) and other arguments. | Obviously, instructions are specific to a particular type of CPU, and the same opcode may mean very different things on different processors. For example, the opcode 0xA9 ($A9) means "Load Accumulator - Immediate" (LDA #) on a 6502, but the same opcode means "Test" (compare bits) on an x86 system. |
| | Other processors encode instructions as bit fields packed with a instruction word. For example, specific bits within an instruction word specify the operation, other bits specify the addressing mode, and still other bits specify the register(s) and other arguments. |
| |
| Thus, the length of each instruction may be variable (6502, x86_64) or fixed (ARM) -- a design decision which affects code density, execution speed, and [[Memory Prefetch|memory prefetch]] operations. | Thus, the length of each instruction may be variable (6502, x86_64) or fixed (ARM) -- a design decision which affects code density, execution speed, and [[Memory Prefetch|memory prefetch]] operations. |
| Machine language is very hard to write and read, although it can be hand-coded on simple processors (it was not uncommon for 6502 programmers to memorize the complete instruction set, for example). It is particularly difficult to write and read when the [[Instruction Set Architecture|ISA]] uses bit-packing. | Machine language is very hard to write and read, although it can be hand-coded on simple processors (it was not uncommon for 6502 programmers to memorize the complete instruction set, for example). It is particularly difficult to write and read when the [[Instruction Set Architecture|ISA]] uses bit-packing. |
| |
| [[Assembly Language]] (or just "Assembly") is closely related to machine language, but uses a [[Symbolic|symbolic]] representation of instructions and memory locations and is therefore easier to write and read. A compiler for assembly language is called an [[Assembler|assembler]], and a tool to convert machine code to assembly is called a [[Disassembler|disassembler]]. | [[Assembly Language]] (or just "Assembly") is closely related to machine language, but uses a [[symbol|symbolic]] representation of instructions and memory locations and is therefore easier to write and read. A compiler for assembly language is called an [[Assembler|assembler]], and a tool to convert machine code to assembly is called a [[Disassembler|disassembler]]. |
| |
| Assembly is [[Portable|architecture-specific]] but allows precise control over the exact instructions which will be executed by the CPU. It is therefore used for the most basic functions of the bootloader and operating system kernel, the lowest-level operating system devices drivers, and code where performance is critical. However, assemblers do not usually perform [[Compiler Optimizations|optimizations]], so code in C or other high-level languages which has been optimized by a good compiler will often perform as well as or better than assembly code unless it is very painstakingly written. | Assembly is [[Portable|architecture-specific]] but allows precise control over the exact instructions which will be executed by the CPU. It is therefore used for the most basic functions of the bootloader and operating system kernel, the lowest-level operating system devices drivers, and code where performance is critical. However, assemblers do not usually perform [[Compiler Optimizations|optimizations]], so code in C or other high-level languages which has been optimized by a good compiler will often perform as well as or better than assembly code unless it is very painstakingly written. |
| |
| Interpretation and compilation represent the two extreme cases of conversion to machine code. There are intermediate approaches between interpreting and compiling: | Interpretation and compilation represent the two extreme cases of conversion to machine code. There are intermediate approaches between interpreting and compiling: |
| * Bytecode compilers and interpreters compile source code into a "bytecode" which is like an architecture-independent machine code. The instructions in the bytecode are effectively instructions for a virtual machine that is not modelled after a physical machine. Therefore, they cannot be directly executed by any CPU, but they can be interpreted much more quickly than the original source code because they have already been partially processed. Java and Python both utilize bytecode in the most common implementations. | * Bytecode compilers and interpreters compile source code into a "bytecode" which is like an architecture-independent machine code. The instructions in the bytecode are effectively instructions for a virtual machine that is not modelled after a physical machine. Therefore, they cannot be directly executed by any CPU, but they can be interpreted much more quickly than the original source code because they have already been partially processed. Java, Python, and [[https://webassembly.org/|Wasm]] all utilize bytecode in the most common implementations. |
| * Just-in-time (JIT) interpreters/compilers take source code or bytecode and compile it into machine code on-the-fly. This has three advantages over traditional compilation: (1) the distributed software can be in an architecture-neutral form, (2) any portion of the code which will not be executed is not compiled, and (3) more information is available to the compiler about the execution environment when the compilation is being performed. JIT execution is typically faster than interpretation, but slower than traditional (pre-)compilation, because the compilation step occurs at run time. | |
| | * Just-in-time (JIT) interpreters/compilers take source code or bytecode and compile it into machine code on-the-fly. This has three advantages over traditional compilation: (1) the distributed software can be in an architecture-neutral form, (2) any portion of the code which will not be executed is not compiled, and (3) more information is available to the compiler about the execution environment when the compilation is being performed, allowing certain advanced optimizations. JIT execution is typically faster than interpretation, but slower than traditional (pre-)compilation, because the compilation step occurs at run time. |
| |
