# Execute instruction

In a computer instruction set architecture (ISA), an execute instruction is a machine language instruction which treats data as a machine instruction and executes it.
It can be considered a fourth mode of instruction sequencing after ordinary sequential execution, branching, and interrupting. Since it is an instruction that operates on other instructions like the repeat instruction, it has also been classified as a meta-instruction.

## Computer models

Many computer families introduced in the 1950s and 1960s include execute instructions: the IBM 709 and IBM 7090 (op code mnemonic: XEC), the IBM 7030 Stretch (EX, EXIC), the PDP-1/-4/-7/-9/-15 (XCT), the UNIVAC 1100/2200 (EXRI), the CDC 924 (XEC), the PDP-6/-10 (XCT), the IBM System/360 (EX), the GE-600/Honeywell 6000 (XEC, XED), the SDS-9xx (EXU), the SDS 92 (EXU), and the SDS Sigma series (EXU).
Fewer 1970s designs include execute instructions: the Nuclear Data 812 minicomputer (1971) (XCT), the HP 3000 (1972) (XEQ), and the Texas Instruments TI-990 (1975) and its microprocessor version, the TMS9900 (1976) (X). The Signetics 8X300 (1976) is a rare microprocessor design with an execute instruction. XEC executes one instruction from a table of 1 to 255 instructions. Most instructions act as single instruction subroutines but branches are used to implement jump tables. An execute instruction was proposed for the PDP-11 in 1970, but never implemented for it or its successor, the VAX.
Modern instruction sets do not include execute instructions because they interfere with pipelining, prefetching, and other optimizations.

## Semantics

The instruction to be executed, the target instruction, may be in a register or fetched from memory. Some architectures allow the target instruction to itself be an execute instruction; others do not.
The target instruction is executed as if it were in the memory location of the execute instruction. If, for example, it is a subroutine call instruction, execution is transferred to the subroutine, with the return location being the location after the execute instruction. However, some architectures implement variants of the execute instruction which inhibit branches.
The System/360 supports variable-length target instructions. It also supports modifying the target instruction before executing it. The target instruction must start on an even-numbered byte.
The GE-600 series supports execution of two-instruction sequences, which must be doubleword-aligned.
Some architectures support an execute instruction which operates in a different protection and address relocation mode. For example, the ITS PDP-10 paging device supports a privileged-mode XCTR 'execute relocated' instruction which allows memory reads, writes, or both to use the user-mode page mappings. Similarly, the KL10 variant of the PDP-10 supports the privileged instruction PXCT 'previous context XCT'.
The execute instruction can cause several problems when one execute instruction points to another one and so on:
* the processor may be uninterruptible for multiple clock cycles if the execute instruction cannot be interrupted in the middle of execution;
* similarly, the processor may go into an infinite loop if the series of execute instructions is circular and uninterruptible;
* if the execute instructions are on different swap pages, all of the pages need to be swapped in for the instruction to complete, which can cause thrashing.
Similar issues arise with multilevel indirect addressing modes.

## Applications

The execute instruction has several applications:
* Functioning as a single-instruction subroutine without the usual overhead of subroutine calls; that instruction may call a full subroutine if necessary.
* Late binding
** Implementation of call by name and other thunks.
** A table of execute targets may be used for dynamic dispatch of the methods or virtual functions of an object or class, especially when the method or function may often be implementable as a single instruction.
** An execute target may contain a hook for adding functionality or for debugging; it is normally initialized as a NOP which may be overridden dynamically.
** An execute target may change between a fast version of an operation and a fully traced version.
* Tracing, monitoring, and emulation
** This may maintain a pseudo-program counter, leaving the normal program counter unchanged.
* Executing dynamically generated code, especially when memory protection prevents executable code from being writable.
* Emulating self-modifying code, especially when it must be reentrant or read-only.
* In the IBM System/360, the execute instruction can modify bits 8-15 of the target instruction, effectively turning an instruction with a fixed argument (e.g., a length field) into an instruction with a variable argument.
* Privileged-mode execute instructions as on the KL10 are used by operating system kernels to execute operations such as block copies within the virtual space of user processes.