NOP

For other uses, see NOP (disambiguation).

In computer science, a NOP or NOOP (short for No Operation) is an assembly language instruction, programming language statement, or computer protocol command that does nothing.

Machine instruction

Some computer instruction sets include an instruction whose explicit purpose is to not change the state of any of the programmer-accessible registers, status flags, or memory and which may require a specific number of clock cycles to execute. In other instruction sets, a NOP has to be simulated by executing an instruction having operands that cause the same effect (e.g., on the SPARC processor, the instruction sethi 0, %g0 is the recommended solution).

A NOP is most commonly used for timing purposes, to force memory alignment, to prevent hazards, to occupy a branch delay slot, to render void an existing instruction such as a jump, or as a place-holder to be replaced by active instructions later on in program development (or to replace removed instructions when refactoring would be problematic or time-consuming). In some cases, a NOP can have minor side effects; for example, on the Motorola 68000 series of processors, the NOP opcode causes a synchronization of the pipeline.

Here are the characteristics of the NOP instruction for some CPU architectures:

CPU architecture	Mnemonic	Bytes	Opcode	Notes
Intel x86 CPU family	NOP	1; 1–9 for i686	0x90; 0x0f 0x1f	0x90 decodes to xchg eax, eax in all modes except long mode, which has no effect. In long mode, the opcode 0x90 has no effect still but is no longer equal to xchg eax, eax.
Intel 8051 / MCS-51 family	NOP	1	0x00
ARM A32	NOP	4	0x00000000	This stands for andeq r0, r0, r0 which has no effect. The assembly instruction nop will most likely expand to mov r0, r0 which is encoded 0xE1A00000.
ARM T32 (16 bit)	NOP	2	0xb000	Opcode for ADD SP, #0 - Add zero to the stack pointer (No operation)
ARM T32 (32 bit)	NOP	4	0xf3af 1000
ARM A64 (64 bit)	NOP	4	0xd503201f
IBM System/360, IBM System/370, UNIVAC Series 90	NOP	4	0x47000000 or 0x470nnnnn or 0x47n0nnnn where "n" is any 4-bit value.	The NOP ("No-Op") and NOPR ("No-Op Register") are a subset of the "Branch on Condition" or "Branch on Condition Register" instructions, respectively, both versions have two options for generating a NO-OP. In the case of both the NOP and NOPR instructions, the first 0 in the second byte is the "mask" value, the condition to test such as equal, not equal, high, low, etc. If the mask is 0, no branch occurs. In the case of the NOPR instruction, the second value in the second byte is the register to branch on. If register 0 is chosen, no branch occurs regardless of the mask value. Thus, if either of the two values in the second byte is 0, the branch will not happen. In the case of the NOP instruction, the second value in the second byte is the "base" register of a combined base register, displacement register and offset address. If the base register is also 0, the branch is not taken regardless of the value of the displacement register or displacement address.
	NOPR	2	0x0700 or 0x070n or 0x07n0 where "n" is any 4-bit value.
SuperH	NOP	2	0x0009
MIPS	NOP	4	0x00000000	Stands for sll r0,r0,0
MIPS-X	NOP	4	0x60000019	(extended opcode for add r0,r0,r0)
MMIX	SWYM	4	0xfd******	SWYM stands for “Sympathize with your machinery.” The * digits can be chosen arbitrarily.
Motorola 68000 family	NOP	2	0x4e71	This synchronizes the pipeline and prevents instruction overlap.
Motorola 6809	NOP	1	0x12
MOS Technology 65xx	NOP	1	0xea	NOP consumes two clock cycles.  Undefined opcodes in the NMOS versions of the 65xx family were converted to be NOPs of varying instruction lengths and cycle times in the 65C02.
PowerPC	NOP	4	0x60000000	(extended opcode for ori r0,r0,0)
PIC microcontroller	NOP	12 bits	0b000000000000
SPARC	NOP	4	0x01000000	Stands for sethi 0, %g0 which zeroes the %g0 register (this has no effect because this SPARC register is hardwired to zero)
Z80	NOP	1	0x00	There are some other instructions without any effect (and the same timing): LD A, A, LD B, B etc.
PDP-11	NOP	16 bits	000240 (octal)
VAX	NOP	1	0x01	Delay is dependent on processor type

From a hardware design point of view, unmapped areas of a bus are often designed to return zeroes; since the NOP slide behavior is often desirable, it gives a bias to coding it with the all-zeroes opcode.

Code

NOP is sometimes used as a description for the action performed by a function or a sequence of programming language statements if the function or code has no effect (it might also be called redundant code). A common compiler optimization is the detection and removal of this kind of code. Such code may be required by the grammar of the programming language, which does not allow a blank.

Ada

In Ada, the null statement serves as a NOP. As the syntax forbids that control statements or functions be empty, the null statement must be used to specify that no action is required. (Thus, if the programmer forgets to write a sequence of statements, the program will fail to compile.)

C and derivatives

The following is an example of a single C statement that behaves like a NOP. In practice, most compilers will not generate code for this statement:

  i+1;

This statement performs an addition and discards the result. Indeed, any statement without side effects (and that does not affect control flow, e.g., break, return) can be removed, as the result of the computation is discarded.

The simplest possible statement in C that behaves like a NOP is the so-called null statement, which is just a semi-colon in a context requiring a statement. (A compiler is not required to generate a NOP instruction in this case; typically, no instructions whatsoever would be generated.)

  ;

Alternatively, an empty block (compound statement) may be used, and may be more legible:

  {}

In some cases, such as the body of a function, a block must be used, but this can be empty. In C, statements cannot be empty – simple statements must end with a ; (semicolon) while compound statements are enclosed in {} (braces), which does not itself need a following semicolon. Thus in contexts where a statement is grammatically required, some such null statement can be used.

The null statement is useless by itself, but it can have a syntactic use in a wider context, e.g., within the context of a loop:

  while (getchar() != '\n') {}

alternatively,

  while (getchar() != '\n')
      ;

or more tersely:

  while (getchar() != '\n');

(note that the last form may be confusing, as semicolon usually indicates an end of function call instruction when placed after a round parenthesis on the end of line).

The above code continues calling the function getchar() until it returns a \n (newline) character, essentially fast-forwarding the current reading location of standard input to the beginning of next line.

Fortran

In Fortran, the CONTINUE statement is used in some contexts such as the last statement in a DO loop, although it can be used anywhere, and does not have any functionality.

Pascal

As with C, the ; used by itself can be used as a null statement. In fact, due to the specification of the language, in a BEGIN / END block, the semicolon is optional before the END statement, thus a semicolon used there is superfluous.

Also, a block consisting of BEGIN END; may be used as a placeholder to indicate no action, even if placed inside another BEGIN / END block.

Python

The Python programming language has a pass statement which has no effect when executed and thus serves as a NOP. It is primarily used to ensure correct syntax due to Python's indentation-sensitive syntax; for example the syntax for definition of a class requires an indented block with the class logic, which has to be expressed as pass when it should be empty.

jQuery

The jQuery library provides a function jQuery.noop(), which does nothing.

Angular

The Angular framework provides angular.noop function that performs no operations.

Shell Scripting (bash, zsh, etc)

The ':' [colon] character is a shell builtin that is the equivalent of a "NOP" (a do-nothing operation). It may be considered a synonym for the shell builtin 'true', and its exit status is true (0).

Visual Basic

The Visual Basic language has a ; statement, which does nothing.

NOP protocol commands

Many computer protocols, such as telnet, include a NOP command that a client can issue to request a response from the server without requesting any other actions. Such a command can be used to ensure the connection is still alive or that the server is responsive. A NOOP command is part of the following protocols (this is a partial list):

• telnet
• FTP
• SMTP
• X11
• POP3
• NNTP
• finger
• IMAP4
• BitTorrent
• Character encoding: the null control character

Note that unlike the other protocols listed, the IMAP4 NOOP command has a specific purpose - it allows the server to send any pending notifications to the client.

While most telnet or FTP servers respond to a NOOP command with "OK" or "+OK", some programmers have added quirky responses to the client. For example, the ftpd daemon of MINIX responds to NOOP with the message:

200 NOOP to you too!

Cracking

NOPs are often involved when cracking software that checks for serial numbers, specific hardware or software requirements, presence or absence of hardware dongles, etc. This is accomplished by altering functions and subroutines to bypass security checks and instead simply return the expected value being checked for. Because most of the instructions in the security check routine will be unused, these would be replaced with NOPs, thus removing the software's security functionality without attracting any attention.

Security exploits

The NOP opcode can be used to form a NOP slide, which allows code to execute when the exact value of the instruction pointer is indeterminate (e.g., when a buffer overflow causes a function's return address on the stack to be overwritten).

See also

• Computer architecture
• HLT (x86 instruction)
• Identity function – the functional programming equivalent to NOOP
• xyzzy (command) – a command sometimes used instead of NOOP
• IEFBR14
• Filler text
• Comment (computer programming) – annotations generally for programmers that are ignored by compilers and interpreters