View source for Assembly language

{{Short description|Low-level programming language family}}
{{Use dmy dates|date=March 2020|cs1-dates=y}}
{{Infobox programming language
| name = Assembly language
| logo = <!-- Filename only -->
| logo caption = 
| screenshot = Motorola 6800 Assembly Language.png
| screenshot caption = Typical ''secondary output'' from an assembler&mdash;showing original assembly language (right) for the [[Motorola]] [[MC6800]] and the assembled form
| paradigm = [[Imperative programming|Imperative]], [[Unstructured programming|unstructured]], often [[metaprogramming]] (through [[Macro (computer science)|macros]]), certain assemblers are [[structured programming|structured]] or [[object-oriented programming|object-oriented]]
| family = 
| designer = <!-- or: | designers = -->
| developer = <!-- or: | developers = -->
| released = {{start date and age|1947|df=yes}}
| latest release version = 
| latest release date = <!-- {{start date and age|YYYY|MM|DD|df=yes}} -->
| typing = None
| scope = 
| programming language = 
| platform = 
| operating system = 
| license = 
| file ext = <code>.asm</code>, <code>.s</code>, <code>.S</code>, <code>.inc</code>, <code>.wla</code>, <code>.SRC</code> as well as several others depending on the assembler
| file format = <!-- or: | file formats = -->
| website = <!-- {{URL|www.example.com}} -->
| implementations = 
| dialects = 
| influenced by = 
| influenced = 
}}

In computing, '''assembly language''' (alternatively '''assembler language'''<ref name="IBM_2014_ASM"/> or '''symbolic machine code'''),<ref name="Ohio_2016"/><ref name="Archer_2016"/><ref name="Streib 2020 p. ">{{cite book | last=Streib | first=James T. | title=Undergraduate Topics in Computer Science | chapter=Guide to Assembly Language | publisher=Springer International Publishing | publication-place=Cham | year=2020 | isbn=978-3-030-35638-5 | issn=1863-7310 | doi=10.1007/978-3-030-35639-2 | page= | s2cid=195930813 | quote=Programming in assembly language has the same benefits as programming in machine language, except it is easier.}}</ref> often referred to simply as '''assembly''' and commonly abbreviated as '''ASM''' or '''asm''', is any [[low-level programming language]] with a very strong correspondence between the instructions in the language and the [[computer architecture|architecture's]] [[machine code]] [[instruction set architecture|instructions]].<ref name="Saxon_1962"/> Assembly language usually has one [[Statement (computer science)|statement]] per machine code instruction (1:1), but  constants, [[Comment (computer programming)|comments]], assembler [[Directive (programming)|directives]],<ref name="Kornelis_2010"/> symbolic [[Label (computer science)|labels]] of, e.g., [[memory location]]s, [[processor register|registers]], and [[Macro instruction|macros]]<ref name="IBM_2014_Macro"/><ref name="IBM_2014_ASM"/> are generally also supported.

The first assembly code in which a language is used to represent machine code instructions is found in [[Kathleen Booth|Kathleen]] and [[Andrew Donald Booth]]'s 1947 work, ''Coding for A.R.C.''.<ref>{{cite book |last1=Booth |first1=Andrew D |last2=Britten |first2=Kathleen HV |title=Coding for A.R.C. |date=1947 |publisher=Institute for Advanced Study, Princeton |url=https://albert.ias.edu/bitstream/handle/20.500.12111/7941/Booth_Britten_Coding_for_ARC_1947.pdf?sequence=1&isAllowed=y |access-date=4 November 2022}}</ref> Assembly code is converted into executable machine code by a [[Utility software|utility program]] referred to as an ''[[Assembler (computing)|assembler]]''. The term "assembler" is generally attributed to [[Maurice Wilkes|Wilkes]], [[David Wheeler (computer scientist)|Wheeler]] and [[Stanley Gill|Gill]] in their 1951 book ''[[The Preparation of Programs for an Electronic Digital Computer]]'',<ref name="Wilkes_1951"/> who, however, used the term to mean "a program that assembles another program consisting of several sections into a single program".<ref name="Fairhead_2017"/> The conversion process is referred to as ''assembly'', as in ''assembling'' the [[source code]]. The computational step when an assembler is processing a program is called ''assembly time''.

Because assembly depends on the machine code instructions, each assembly language<ref group=nb>Other than meta-assemblers</ref> is specific to a particular [[computer architecture]] such as [[x86]] or [[ARM architecture family|ARM]].<ref name="OS360_2011"/><ref name="Austerlitz 2003 pp. 326–360">{{cite book | last=Austerlitz | first=Howard | title=Data Acquisition Techniques Using PCs | chapter=Computer Programming Languages | publisher=Elsevier | year=2003 | doi=10.1016/b978-012068377-2/50013-9 | pages=326–360 | isbn=9780120683772 | quote=Assembly language (or Assembler) is a compiled, low-level computer language. It is processor-dependent since it basically translates the Assembler's mnemonics directly into the commands a particular CPU understands, on a one-to-one basis. These Assembler mnemonics are the instruction set for that processor.}}</ref><ref name="Carnes 2022">{{cite web |last=Carnes |first=Beau |date=2022-04-27 |title=Learn Assembly Language Programming with ARM |url=https://www.freecodecamp.org/news/learn-assembly-language-programming-with-arm/ |access-date=2022-06-21 |website=freeCodeCamp.org |language=en-US |quote=Assembly language is often specific to a particular computer architecture so there are multiple types of assembly languages. ARM is an increasingly popular assembly language.}}</ref>

Sometimes there is more than one assembler for the same architecture, and sometimes an assembler is specific to an [[operating system]] or to particular operating systems. Most assembly languages do not provide specific [[Syntax (programming languages)|syntax]] for operating system calls, and most assembly languages can be used universally with any operating system,<ref group=nb>However, that does not mean that the assembler programs implementing those languages are universal.</ref> as the language provides access to all the real capabilities of the [[Processor (computing)|processor]], upon which all [[system call]] mechanisms ultimately rest. In contrast to assembly languages, most [[high-level programming language]]s are generally [[porting|portable]] across multiple architectures but require [[Interpreter (computing)|interpreting]] or [[Compiler|compiling]], much more complicated tasks than assembling.

In the first decades of computing, it was commonplace for both [[systems programming]] and [[application programming]] to take place entirely in assembly language.  While still irreplaceable for some purposes, the majority of programming is now conducted in higher-level interpreted and compiled languages.  In "[[No Silver Bullet]]", [[Fred Brooks]] summarised the effects of the switch away from assembly language programming: "Surely the most powerful stroke for software productivity, reliability, and simplicity has been the progressive use of high-level languages for programming. Most observers credit that development with at least a factor of five in productivity, and with concomitant gains in reliability, simplicity, and comprehensibility."<ref name="Brooks_1986_NSB"/>

Today, it is typical to use small amounts of assembly language code within larger systems implemented in a higher-level language, for performance reasons or to interact directly with hardware in ways unsupported by the higher-level language.  For instance, just under 2% of version 4.9 of the [[Linux kernel]] source code is written in assembly; more than 97% is written in [[C (programming language)|C]].<ref name="Anguiano_kernel_sloccount">{{Cite web | author-last=Anguiano | author-first = Ricardo | title=linux kernel mainline 4.9 sloccount.txt |url=https://gist.github.com/ricardoanguiano/18125b7eb3f26cf83724fb60662bdd2c |access-date=2022-05-04 |website=Gist |language=en}}</ref>

==Assembly language syntax==
Assembly language uses a [[mnemonic]] to represent, e.g., each low-level [[machine code|machine instruction]] or [[opcode]], each [[directive (programming)|directive]], typically also each [[register (computing)#ARCHITECTURAL|architectural register]], [[bit field|flag]], etc. Some of the mnemonics may be built-in and some user-defined. Many operations require one or more [[Operand#Computer science|operands]] in order to form a complete instruction. Most assemblers permit named constants, registers, and [[Label (computer science)|labels]] for program and memory locations, and can calculate [[Expression (computer science)|expressions]] for operands. Thus, programmers are freed from tedious repetitive calculations and assembler programs are much more readable than machine code. Depending on the architecture, these elements may also be combined for specific instructions or [[addressing mode]]s using [[offset (computer science)|offset]]s or other data as well as fixed addresses. Many assemblers offer additional mechanisms to facilitate program development, to control the assembly process, and to aid [[debugging]].

Some are column oriented, with specific fields in specific columns; this was very common for machines using [[punched card]]s in the 1950s and early 1960s. Some assemblers have free-form syntax, with fields separated by delimiters, e.g., punctuation, [[Whitespace character|white space]]. Some assemblers are hybrid, with, e.g., labels, in a specific column and other fields separated by delimiters; this became more common than column-oriented syntax in the 1960s.

==Terminology==
* A '''macro assembler''' is an assembler that includes a [[macro (computer science)|macroinstruction]] facility so that (parameterized) assembly language text can be represented by a name, and that name can be used to insert the expanded text into other code.
** '''Open code''' refers to any assembler input outside of a macro definition.
* {{anchor|Cross assembler}}A '''cross assembler''' (see also [[cross compiler]]) is an assembler that is run on a computer or [[operating system]] (the ''host'' system) of a different type from the system on which the resulting code is to run (the ''target system''). Cross-assembling facilitates the development of programs for systems that do not have the resources to support software development, such as an [[embedded system]] or a [[microcontroller]]. In such a case, the resulting [[object code]] must be transferred to the target system, via [[read-only memory]] (ROM, [[EPROM]], etc.), a [[Programmer (hardware)|programmer]] (when the read-only memory is integrated in the device, as in microcontrollers), or a data link using either an exact bit-by-bit copy of the object code or a text-based representation of that code (such as [[Intel hex]] or [[Motorola S-record]]).
* A '''[[high-level assembler]]''' is a program that provides language abstractions more often associated with high-level languages, such as advanced control structures ([[Conditional (computer programming)#If–then(–else)|IF/THEN/ELSE]], DO CASE, etc.) and high-level abstract data types, including structures/records, unions, classes, and sets.
* A '''[[microassembler]]''' is a program that helps prepare a [[microcode|microprogram]] to control the low level operation of a computer.
* A '''meta-assembler''' is "a program that accepts the syntactic and semantic description of an assembly language, and generates an assembler for that language",<ref name="Daintith_2019"/> or that accepts an assembler source file along with such a description and assembles the source file in accordance with that description. "Meta-Symbol" assemblers for the [[SDS 9 Series]] and [[SDS Sigma series]] of computers are meta-assemblers.<ref>{{cite book |last1=Xerox Data Systems |title=Xerox Meta-Symbol Sigma 5-9 Computers Language and Operations Reference Manual |date=Oct 1975 |page=vi |url=http://bitsavers.org/pdf/sds/sigma/lang/900952G_metaSymbolLangRef_Oct75.pdf |quote=Used as a meta-assembler, it enables the user to design his own programming languages and to generate processors for such languages with a minimum of effort. |archive-url=https://ghostarchive.org/archive/20221009/http://bitsavers.org/pdf/sds/sigma/lang/900952G_metaSymbolLangRef_Oct75.pdf |archive-date=2022-10-09 |url-status=live |access-date=June 7, 2020}}</ref> [[Sperry Univac]] also provided a Meta-Assembler for the [[UNIVAC 1100/2200 series]].<ref>{{cite book |last1=Sperry Univac Computer Systems |title=Sperry Univac Computer Systems Meta-Assembler (MASM) Programmer Reference |date=1977 |url=http://www.bitsavers.org/pdf/univac/1100/asm/UP-8453_MASM_Programmers_Ref_1977.pdf |archive-url=https://ghostarchive.org/archive/20221009/http://www.bitsavers.org/pdf/univac/1100/asm/UP-8453_MASM_Programmers_Ref_1977.pdf |archive-date=2022-10-09 |url-status=live |access-date=June 7, 2020}}</ref>
* '''[[inline assembler]]''' (or '''embedded assembler''') is assembler code contained within a high-level language program.<ref>{{cite web |title=How to Use Inline Assembly Language in C Code |url=https://gcc.gnu.org/onlinedocs/gcc/Using-Assembly-Language-with-C.html |website=gnu.org |access-date=Nov 5, 2020}}</ref> This is most often used in systems programs which need direct access to the hardware.

==Key concepts==
===Assembler===<!-- This section is linked from [[Computer software]] -->
An '''assembler''' program creates [[object code]] by [[translator (computing)|translating]] combinations of [[mnemonic]]s and [[Syntax (programming languages)|syntax]] for operations and addressing modes into their numerical equivalents. This representation typically includes an ''operation code'' ("[[opcode]]") as well as other control [[bit]]s and data. The assembler also calculates constant expressions and resolves [[identifier|symbolic names]] for memory locations and other entities.<ref name="Salomon_1992"/> The use of symbolic references is a key feature of assemblers, saving tedious calculations and manual address updates after program modifications. Most assemblers also include [[Macro (computer science)|macro]] facilities for performing textual substitution – e.g., to generate common short sequences of instructions as [[inline expansion|inline]], instead of ''called'' [[subroutine]]s.

Some assemblers may also be able to perform some simple types of [[instruction set architecture|instruction set]]-specific [[compiler optimization|optimization]]s. One concrete example of this may be the ubiquitous [[x86]] assemblers from various vendors. Called [[jump-sizing]],<ref name="Salomon_1992"/> most of them are able to perform jump-instruction replacements (long jumps replaced by short or relative jumps) in any number of passes, on request. Others may even do simple rearrangement or insertion of instructions, such as some assemblers for [[RISC architectures]] that can help optimize a sensible [[instruction scheduling]] to exploit the [[CPU pipeline]] as efficiently as possible.<ref>{{cite conference |url=https://www.researchgate.net/publication/262389375 |doi=10.1145/2465554.2465559 |title=Improving processor efficiency by statically pipelining instructions |book-title=Proceedings of the 14th ACM SIGPLAN/SIGBED conference on Languages, compilers and tools for embedded systems |year=2013 |last1=Finlayson |first1=Ian |last2=Davis |first2=Brandon |last3=Gavin |first3=Peter |last4=Uh |first4=Gang-Ryung |last5=Whalley |first5=David |last6=Själander |first6=Magnus |last7=Tyson |first7=Gary |pages=33–44 |isbn=9781450320856 |s2cid=8015812}}</ref>

Assemblers have been available since the 1950s, as the first step above machine language and before [[high-level programming language]]s such as [[Fortran]], [[ALGOL|Algol]], [[COBOL]] and [[Lisp (programming language)|Lisp]]. There have also been several classes of translators and semi-automatic [[code generation (compiler)|code generators]] with properties similar to both assembly and high-level languages, with [[Speedcode]] as perhaps one of the better-known examples.

There may be several assemblers with different [[Syntax (programming languages)|syntax]] for a particular [[Central processing unit|CPU]] or [[instruction set architecture]]. For instance, an instruction to add memory data to a register in a [[x86]]-family processor might be <code>add eax,[ebx]</code>, in original ''[[Intel syntax]]'', whereas this would be written <code>addl (%ebx),%eax</code> in the ''[[AT&T syntax]]'' used by the [[GNU Assembler]]. Despite different appearances, different syntactic forms generally generate the same numeric [[machine code]]. A single assembler may also have different modes in order to support variations in syntactic forms as well as their exact semantic interpretations (such as [[FASM]]-syntax, [[Turbo Assembler|TASM]]-syntax, ideal mode, etc., in the special case of [[x86 assembly language|x86 assembly]] programming).

==== {{Anchor|Two-pass assembler}} Number of passes====
There are two types of assemblers based on how many passes through the source are needed (how many times the assembler reads the source) to produce the object file.
* '''One-pass assemblers''' process the source code once.  For symbols used before they are defined, the assembler will emit [[Erratum|"errata"]] after the eventual definition, telling the [[linker (computing)|linker]] or the loader to patch the locations where the as yet undefined symbols had been used.
* '''Multi-pass assemblers''' create a table with all symbols and their values in the first passes, then use the table in later passes to generate code.
In both cases, the assembler must be able to determine the size of each instruction on the initial passes in order to calculate the addresses of subsequent symbols. This means that if the size of an operation referring to an operand defined later depends on the type or distance of the operand, the assembler will make a pessimistic estimate when first encountering the operation, and if necessary, pad it with one or more
"[[NOP (code)|no-operation]]" instructions in a later pass or the errata. In an assembler with [[peephole optimization]], addresses may be recalculated between passes to allow replacing pessimistic code with code tailored to the exact distance from the target.

The original reason for the use of one-pass assemblers was memory size and speed of assembly – often a second pass would require storing the symbol table in memory (to handle [[forward reference]]s), rewinding and rereading the program source on [[magnetic-tape data storage|tape]], or rereading a deck of [[punched card|cards]] or [[punched tape|punched paper tape]]. Later computers with much larger memories (especially disc storage), had the space to perform all necessary processing without such re-reading. The advantage of the multi-pass assembler is that the absence of errata makes the [[linker (computing)|linking process]] (or the [[loader (computing)|program load]] if the assembler directly produces executable code) faster.<ref name="Beck_1996"/>

'''Example:''' in the following code snippet, a one-pass assembler would be able to determine the address of the backward reference <var>BKWD</var> when assembling statement <var>S2</var>, but would not be able to determine the address of the forward reference <var>FWD</var> when assembling the branch statement <var>S1</var>; indeed, <var>FWD</var> may be undefined. A two-pass assembler would determine both addresses in pass 1, so they would be known when generating code in pass 2.
 {{var|S1}}   B    {{var|FWD}}
   ...
 {{var|FWD}}   EQU *
   ...
 {{var|BKWD}}  EQU *
   ...
 {{var|S2}}    B   {{var|BKWD}}

====High-level assemblers====
More sophisticated [[high-level assembler]]s provide language abstractions such as:
* High-level procedure/function declarations and invocations
* Advanced control structures (IF/THEN/ELSE, SWITCH)
* High-level abstract data types, including structures/records, unions, classes, and sets
* Sophisticated macro processing (although available on ordinary assemblers since the late 1950s for, e.g., the [[IBM 700/7000 series|IBM 700 series]] and [[IBM 700/7000 series|IBM 7000 series]], and since the 1960s for [[IBM System/360]] (S/360), amongst other machines)
* [[Object-oriented programming]] features such as [[class (computer programming)|class]]es, [[Object (computer science)|object]]s, [[Abstraction (computer science)|abstraction]], [[Polymorphism (computer science)|polymorphism]], and [[inheritance (object-oriented programming)|inheritance]]<ref name="Hyde_2003"/>
See [[#Language design|Language design]] below for more details.

===Assembly language===
A program written in assembly language consists of a series of [[mnemonic]] processor instructions and meta-statements (known variously as declarative operations, directives, pseudo-instructions, pseudo-operations and pseudo-ops), comments and data. Assembly language instructions usually consist of an [[opcode]] mnemonic followed by an [[Operand#Computer science|operand]], which might be a list of data, arguments or parameters.<ref name="Intel_1999"/>  Some instructions may be "implied", which means the data upon which the instruction operates is implicitly defined by the instruction itself—such an instruction does not take an operand.  The resulting statement is translated by an [[assembly language assembler|assembler]] into [[machine language]] instructions that can be loaded into memory and executed.

For example, the instruction below tells an [[x86]]/[[IA-32]] processor to move an [[Constant (computer programming)|immediate 8-bit value]] into a [[processor register|register]]. The [[binary code]] for this instruction is 10110 followed by a 3-bit identifier for which register to use. The identifier for the ''AL'' register is 000, so the following [[machine code]] loads the ''AL'' register with the data 01100001.<ref name="Intel_1999"/>
 10110000 01100001
This binary computer code can be made more human-readable by expressing it in [[hexadecimal]] as follows.
 B0 61
Here, <code>B0</code> means "Move a copy of the following value into ''AL''", and <code>61</code> is a hexadecimal representation of the value 01100001, which is 97 in [[decimal]]. Assembly language for the 8086 family provides the [[mnemonic]] [[MOV (x86 instruction)|MOV]] (an abbreviation of ''move'') for instructions such as this, so the machine code above can be written as follows in assembly language, complete with an explanatory comment if required, after the semicolon. This is much easier to read and to remember.
<syntaxhighlight lang="nasm">MOV AL, 61h       ; Load AL with 97 decimal (61 hex)</syntaxhighlight>

In some assembly languages (including this one) the same mnemonic, such as MOV, may be used for a family of related instructions for loading, copying and moving data, whether these are immediate values, values in registers, or memory locations pointed to by values in registers or by immediate (a.k.a. direct) addresses.  Other assemblers may use separate opcode mnemonics such as L for "move memory to register", ST for "move register to memory", LR for "move register to register", MVI for "move immediate operand to memory", etc.

If the same mnemonic is used for different instructions, that means that the mnemonic corresponds to several different binary instruction codes, excluding data (e.g. the <code>61h</code> in this example), depending on the operands that follow the mnemonic.  For example, for the x86/IA-32 CPUs, the Intel assembly language syntax <code>MOV AL, AH</code> represents an instruction that moves the contents of register ''AH'' into register ''AL''. The<ref group="nb" name="NB3"/> hexadecimal form of this instruction is:
 88 E0
The first byte, 88h, identifies a move between a byte-sized register and either another register or memory, and the second byte, E0h, is encoded (with three bit-fields) to specify that both operands are registers, the source is ''AH'', and the destination is ''AL''.

In a case like this where the same mnemonic can represent more than one binary instruction, the assembler determines which instruction to generate by examining the operands.  In the first example, the operand <code>61h</code> is a valid hexadecimal numeric constant and is not a valid register name, so only the <code>B0</code> instruction can be applicable.  In the second example, the operand <code>AH</code> is a valid register name and not a valid numeric constant (hexadecimal, decimal, octal, or binary), so only the <code>88</code> instruction can be applicable.

Assembly languages are always designed so that this sort of lack of ambiguity is universally enforced by their syntax.  For example, in the Intel x86 assembly language, a hexadecimal constant must start with a numeral digit, so that the hexadecimal number 'A' (equal to decimal ten) would be written as <code>0Ah</code> or <code>0AH</code>, not <code>AH</code>, specifically so that it cannot appear to be the name of register ''AH''.  (The same rule also prevents ambiguity with the names of registers ''BH'', ''CH'', and ''DH'', as well as with any user-defined symbol that ends with the letter ''H'' and otherwise contains only characters that are hexadecimal digits, such as the word "BEACH".)

Returning to the original example, while the x86 opcode 10110000 (<code>B0</code>) copies an 8-bit value into the ''AL'' register, 10110001 (<code>B1</code>) moves it into ''CL'' and 10110010 (<code>B2</code>) does so into ''DL''. Assembly language examples for these follow.<ref name="Intel_1999"/>
<syntaxhighlight lang="nasm">
MOV AL, 1h        ; Load AL with immediate value 1
MOV CL, 2h        ; Load CL with immediate value 2
MOV DL, 3h        ; Load DL with immediate value 3
</syntaxhighlight>
The syntax of MOV can also be more complex as the following examples show.<ref name="Evans_2006"/>
<syntaxhighlight lang="nasm">
MOV EAX, [EBX]	  ; Move the 4 bytes in memory at the address contained in EBX into EAX
MOV [ESI+EAX], CL ; Move the contents of CL into the byte at address ESI+EAX
MOV DS, DX        ; Move the contents of DX into segment register DS
</syntaxhighlight>
<!-- The MOV to/from segment register opcodes are included below, so an example involving a segment register should be included. -->
In each case, the MOV mnemonic is translated directly into one of the opcodes 88-8C, 8E, A0-A3, B0-BF, C6 or C7 by an assembler, and the programmer normally does not have to know or remember which.<ref name="Intel_1999"/>

Transforming assembly language into machine code is the job of an assembler, and the reverse can at least partially be achieved by a [[disassembler]]. Unlike [[high-level programming language|high-level languages]], there is a [[bijection|one-to-one correspondence]] between many simple assembly statements and machine language instructions. However, in some cases, an assembler may provide ''pseudoinstructions'' (essentially macros) which expand into several machine language instructions to provide commonly needed functionality. For example, for a machine that lacks a "branch if greater or equal" instruction, an assembler may provide a pseudoinstruction that expands to the machine's "set if less than" and "branch if zero (on the result of the set instruction)". Most full-featured assemblers also provide a rich [[macro (computer science)|macro]] language (discussed below) which is used by vendors and programmers to generate more complex code and data sequences. Since the information about pseudoinstructions and macros defined in the assembler environment is not present in the object program, a disassembler cannot reconstruct the macro and pseudoinstruction invocations but can only disassemble the actual machine instructions that the assembler generated from those abstract assembly-language entities. Likewise, since comments in the assembly language source file are ignored by the assembler and have no effect on the object code it generates, a disassembler is always completely unable to recover source comments.

Each [[computer architecture]] has its own machine language.  Computers differ in the number and type of operations they support, in the different sizes and numbers of registers, and in the representations of data in storage. While most general-purpose computers are able to carry out essentially the same functionality, the ways they do so differ; the corresponding assembly languages reflect these differences.

Multiple sets of [[mnemonic]]s or assembly-language syntax may exist for a single instruction set, typically instantiated in different assembler programs. In these cases, the most popular one is usually that supplied by the CPU manufacturer and used in its documentation.

Two examples of CPUs that have two different sets of mnemonics are the Intel 8080 family and the Intel 8086/8088.  Because Intel claimed copyright on its assembly language mnemonics (on each page of their documentation published in the 1970s and early 1980s, at least), some companies that independently produced CPUs compatible with Intel instruction sets invented their own mnemonics.  The [[Zilog Z80]] CPU, an enhancement of the [[Intel 8080A]], supports all the 8080A instructions plus many more; Zilog invented an entirely new assembly language, not only for the [[Z80 instruction set|new instructions]] but also for all of the 8080A instructions.  For example, where Intel uses the mnemonics ''MOV'', ''MVI'', ''LDA'', ''STA'', ''LXI'', ''LDAX'', ''STAX'', ''LHLD'', and ''SHLD'' for various data transfer instructions, the Z80 assembly language uses the mnemonic ''LD'' for all of them.  A similar case is the [[NEC V20]] and [[NEC V30|V30]] CPUs, enhanced copies of the Intel 8086 and 8088, respectively.  Like Zilog with the Z80, NEC invented new mnemonics for all of the 8086 and 8088 instructions, to avoid accusations of infringement of Intel's copyright.  (It is questionable whether such copyrights can be valid, and later CPU companies such as [[AMD]]<ref group="nb" name="NB1"/> and [[Cyrix]] republished Intel's x86/IA-32 instruction mnemonics exactly with neither permission nor legal penalty.)  It is doubtful whether in practice many people who programmed the V20 and V30 actually wrote in NEC's assembly language rather than Intel's; since any two assembly languages for the same instruction set architecture are isomorphic (somewhat like English and [[Pig Latin]]), there is no requirement to use a manufacturer's own published assembly language with that manufacturer's products.

=== "Hello, world!" on x86 Linux ===
In 32-bit assembly language for Linux on an [[x86]] processor, "Hello, world!" can be printed like this.
<syntaxhighlight lang="nasm">
section	.text
   global _start
	
_start:	        
   mov	edx,len     ; length of string, third argument to write()
   mov	ecx,msg     ; address of string, second argument to write()
   mov	ebx,1       ; file descriptor (standard output), first argument to write()
   mov	eax,4       ; system call number for write()
   int	0x80        ; system call trap
	
   mov	ebx,0       ; exit code, first argument to exit()
   mov	eax,1       ; system call number for exit()
   int	0x80        ; system call trap

section	.data
msg db 'Hello, world!', 0xa  
len equ $ - msg
</syntaxhighlight>

==Language design==
===Basic elements===
There is a large degree of diversity in the way the authors of assemblers categorize statements and in the nomenclature that they use. In particular, some describe anything other than a machine mnemonic or extended mnemonic as a pseudo-operation (pseudo-op). A typical assembly language consists of 3 types of instruction statements that are used to define program operations:

* [[Opcode]] mnemonics
* Data definitions
* Assembly directives

===={{anchor|Mnemonics}}Opcode mnemonics and extended mnemonics====
Instructions (statements) in assembly language are generally very simple, unlike those in [[high-level programming language|high-level languages]]. Generally, a mnemonic is a symbolic name for a single executable machine language instruction (an [[opcode]]), and there is at least one opcode mnemonic defined for each machine language instruction. Each instruction typically consists of an ''operation'' or ''opcode'' plus zero or more ''[[operand]]s''. Most instructions refer to a single value or a pair of values.  Operands can be immediate (value coded in the instruction itself), registers specified in the instruction or implied, or the addresses of data located elsewhere in storage. This is determined by the underlying processor architecture: the assembler merely reflects how this architecture works. ''Extended mnemonics'' are often used to specify a combination of an opcode with a specific operand, e.g., the System/360 assemblers use {{code|B}} as an extended mnemonic for {{code|BC}} with a mask of 15 and {{code|NOP}} ("NO OPeration" – do nothing for one step) for {{code|BC}} with a mask of 0.

''Extended mnemonics'' are often used to support specialized uses of instructions, often for purposes not obvious from the instruction name. For example, many CPU's do not have an explicit NOP instruction, but do have instructions that can be used for the purpose. In 8086 CPUs the instruction {{code|2=asm|xchg ax,ax}} is used for {{code|nop}}, with {{code|nop}} being a pseudo-opcode to encode the instruction {{code|2=asm|xchg ax,ax}}. Some disassemblers recognize this and will decode the {{code|2=asm|xchg ax,ax}} instruction as {{code|nop}}. Similarly, IBM assemblers for [[IBM System/360|System/360]] and [[IBM System/370|System/370]] use the extended mnemonics {{code|NOP}} and {{code|NOPR}} for {{code|BC}} and {{code|BCR}} with zero masks.  For the SPARC architecture, these are known as ''synthetic instructions''.<ref name="SPARC_1992"/>

Some assemblers also support simple built-in macro-instructions that generate two or more machine instructions. For instance, with some Z80 assemblers the instruction {{code|ld hl,bc}} is recognized to generate {{code|ld l,c}} followed by {{code|ld h,b}}.<ref name="Moxham_1996"/> These are sometimes known as ''pseudo-opcodes''.

Mnemonics are arbitrary symbols; in 1985 the [[Institute of Electrical and Electronics Engineers|IEEE]] published Standard 694 for a uniform set of mnemonics to be used by all assemblers.<ref>{{cite book |title=IEEE Std 694-1985: IEEE Standard for Microprocessor Assembly Language |publisher=IEEE Computer Society |date=1985 |isbn=0-7381-2752-3 |oclc=1415906564 }}</ref> The standard has since been withdrawn.

====Data directives====
There are instructions used to define data elements to hold data and variables.  They define the type of data, the length and the [[data structure alignment|alignment]] of data. These instructions can also define whether the data is available to outside programs (programs assembled separately) or only to the program in which the data section is defined. Some assemblers classify these as pseudo-ops.

====Assembly directives====
Assembly directives, also called pseudo-opcodes, pseudo-operations or pseudo-ops, are commands given to an assembler "directing it to perform operations other than assembling instructions".<ref name="Salomon_1992"/> Directives affect how the assembler operates and "may affect the object code, the symbol table, the listing file, and the values of internal assembler parameters". Sometimes the term ''pseudo-opcode'' is reserved for directives that generate object code, such as those that generate data.<ref name="Hyde_MASM"/>

The names of pseudo-ops often start with a dot to distinguish them from machine instructions.  Pseudo-ops can make the assembly of the program dependent on parameters input by a programmer, so that one program can be assembled in different ways, perhaps for different applications. Or, a pseudo-op can be used to manipulate presentation of a program to make it easier to read and maintain. Another common use of pseudo-ops is to reserve storage areas for run-time data and optionally initialize their contents to known values.

Symbolic assemblers let programmers associate arbitrary names (''[[label (computer science)|label]]s'' or ''symbols'') with memory locations and various constants. Usually, every constant and variable is given a name so instructions can reference those locations by name, thus promoting [[self-documenting code]]. In executable code, the name of each subroutine is associated with its entry point, so any calls to a subroutine can use its name. Inside subroutines, [[GOTO]] destinations are given labels. Some assemblers support ''local symbols'' which are often lexically distinct from normal symbols (e.g., the use of "10$" as a GOTO destination).

Some assemblers, such as [[Netwide Assembler|NASM]], provide flexible symbol management, letting programmers manage different [[namespace]]s, automatically calculate offsets within [[data structure]]s, and assign labels that refer to literal values or the result of simple computations performed by the assembler. Labels can also be used to initialize constants and variables with relocatable addresses.

Assembly languages, like most other computer languages, allow comments to be added to program [[source code]] that will be ignored during assembly. Judicious commenting is essential in assembly language programs, as the meaning and purpose of a sequence of binary machine instructions can be difficult to determine. The "raw" (uncommented) assembly language generated by compilers or disassemblers is quite difficult to read when changes must be made.

===Macros===
Many assemblers support ''predefined macros'', and others support ''programmer-defined'' (and repeatedly re-definable) macros involving sequences of text lines in which variables and constants are embedded. The macro definition is most commonly<ref group="nb" name="NB4"/> a mixture of assembler statements, e.g., directives, symbolic machine instructions, and templates for assembler statements. This sequence of text lines may include opcodes or directives. Once a macro has been defined its name may be used in place of a mnemonic. When the assembler processes such a statement, it replaces the statement with the text lines associated with that macro, then processes them as if they existed in the source code file (including, in some assemblers, expansion of any macros existing in the replacement text). Macros in this sense date to IBM [[autocoder]]s of the 1950s.<ref name="Autocoder"/>

'''Macro assemblers''' typically have directives to, e.g., define macros, define variables, set variables to the result of an arithmetic, logical or string expression, iterate, conditionally generate code. Some of those directives may be restricted to use within a macro definition, e.g., '''MEXIT''' in [[HLASM]], while others may be permitted within open code (outside macro definitions), e.g., '''AIF''' and '''COPY''' in HLASM.

In assembly language, the term "macro" represents a more comprehensive concept than it does in some other contexts, such as the [[pre-processor]] in the [[C (programming language)|C programming language]], where its #define directive typically is used to create short single line macros. Assembler macro instructions, like macros in [[PL/I]] and some other languages, can be lengthy "programs" by themselves, executed by interpretation by the assembler during assembly.

Since macros can have 'short' names but expand to several or indeed many lines of code, they can be used to make assembly language programs appear to be far shorter, requiring fewer lines of source code, as with higher level languages. They can also be used to add higher levels of structure to assembly programs, optionally introduce embedded debugging code via parameters and other similar features.

Macro assemblers often allow macros to take [[parameter (computer programming)|parameter]]s. Some assemblers include quite sophisticated macro languages, incorporating such high-level language elements as optional parameters, symbolic variables, conditionals, string manipulation, and arithmetic operations, all usable during the execution of a given macro, and allowing macros to save context or exchange information. Thus a macro might generate numerous assembly language instructions or data definitions, based on the macro arguments. This could be used to generate record-style data structures or "[[loop unrolling|unrolled]]" loops, for example, or could generate entire algorithms based on complex parameters. For instance, a "sort" macro could accept the specification of a complex sort key and generate code crafted for that specific key, not needing the run-time tests that would be required for a general procedure interpreting the specification. An organization using assembly language that has been heavily extended using such a macro suite can be considered to be working in a higher-level language since such programmers are not working with a computer's lowest-level conceptual elements. Underlining this point, macros were used to implement an early [[virtual machine]] in [[SNOBOL4]] (1967), which was written in the SNOBOL Implementation Language (SIL), an assembly language for a virtual machine. The target machine would translate this to its native code using a [[macro assembler]].<ref name="Griswold_1972"/> This allowed a high degree of portability for the time.

Macros were used to customize large scale software systems for specific customers in the mainframe era and were also used by customer personnel to satisfy their employers' needs by making specific versions of manufacturer operating systems. This was done, for example, by systems programmers working with [[IBM]]'s Conversational Monitor System / Virtual Machine ([[VM (operating system)|VM/CMS]]) and with IBM's "real time transaction processing" add-ons, Customer Information Control System [[CICS]], and [[IBM Airline Control Program|ACP]]/[[Transaction Processing Facility|TPF]], the airline/financial system that began in the 1970s and still runs many large [[computer reservation system]]s (CRS) and credit card systems today.

It is also possible to use solely the macro processing abilities of an assembler to generate code written in completely different languages, for example, to generate a version of a program in [[COBOL]] using a pure macro assembler program containing lines of COBOL code inside assembly time operators instructing the assembler to generate arbitrary code. IBM [[OS/360 and successors|OS/360]] uses macros to perform [[system generation]]. The user specifies options by coding a series of assembler macros.  Assembling these macros generates a [[job stream]] to build the system, including [[job control language]] and [[Support programs for OS/360 and successors|utility]] control statements.

This is because, as was realized in the 1960s, the concept of "macro processing" is independent of the concept of "assembly", the former being in modern terms more word processing, text processing, than generating object code. The concept of macro processing appeared, and appears, in the C programming language, which supports "preprocessor instructions" to set variables, and make conditional tests on their values. Unlike certain previous macro processors inside assemblers, the C preprocessor is not [[Turing completeness|Turing-complete]] because it lacks the ability to either loop or "go to", the latter allowing programs to loop.

Despite the power of macro processing, it fell into disuse in many high level languages (major exceptions being [[C (programming language)|C]], [[C++]] and PL/I) while remaining a perennial for assemblers.

Macro parameter substitution is strictly by name: at macro processing time, the value of a parameter is textually substituted for its name. The most famous class of bugs resulting was the use of a parameter that itself was an expression and not a simple name when the macro writer expected a name. In the macro:

 foo: macro a
 load a*b

the intention was that the caller would provide the name of a variable, and the "global" variable or constant b would be used to multiply "a". If foo is called with the parameter <code>a-c</code>, the macro expansion of <code>load a-c*b</code> occurs.  To avoid any possible ambiguity, users of macro processors can parenthesize formal parameters inside macro definitions, or callers can parenthesize the input parameters.<ref name="Microsoft_2012_Macros"/>

===Support for structured programming===
<!-- With rare exceptions, macros are not part of the assembler but reside in the source code or in macro libraries. -->
Packages of macros have been written providing [[structured programming]] elements to encode execution flow. The earliest example of this approach was in the [[Concept-14 macro set]],<ref name="Kessler_1970"/> originally proposed by [[Harlan Mills]] (March 1970), and implemented by Marvin Kessler at IBM's Federal Systems Division, which provided IF/ELSE/ENDIF and similar control flow blocks for OS/360 assembler programs. This was a way to reduce or eliminate the use of [[GOTO]] operations in assembly code, one of the main factors causing [[spaghetti code]] in assembly language. This approach was widely accepted in the early 1980s (the latter days of large-scale assembly language use). IBM's High Level Assembler Toolkit<ref>{{cite web
 |     title = High Level Assembler Toolkit Feature Increases Programmer Productivity
 |        id = A95-1432
 |      date = December 12, 1995
 |       url = https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/649/ENUSA95-1432/index.html&request_locale=en
 | work      = Announcement Letters
 | publisher = [[IBM]]
 | archive-url = https://web.archive.org/web/20230307045942/https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/649/ENUSA95-1432/index.html&request_locale=en
 | archive-date = March 7, 2023
 | url-status = dead
 }}
</ref> includes such a macro package.

Another design was [[A-Natural]],<ref>{{Cite book |last=Whitesmiths Ltd |url=http://archive.org/details/a-natural-manual |title=A-Natural Language Reference Manual |date=1980-07-15}}</ref> a "stream-oriented" assembler for 8080/[[Zilog Z80|Z80]] processors from [[Whitesmiths|Whitesmiths Ltd.]] (developers of the [[Unix]]-like [[Idris (operating system)|Idris]] operating system, and what was reported to be the first commercial [[C (programming language)|C]] [[compiler]]). The language was classified as an assembler because it worked with raw machine elements such as [[opcode]]s, [[processor register|registers]], and memory references; but it incorporated an expression syntax to indicate execution order. Parentheses and other special symbols, along with block-oriented structured programming constructs, controlled the sequence of the generated instructions. A-natural was built as the object language of a C compiler, rather than for hand-coding, but its logical syntax won some fans.

There has been little apparent demand for more sophisticated assemblers since the decline of large-scale assembly language development.<ref name="assembly-language?cat=technology"/> In spite of that, they are still being developed and applied in cases where resource constraints or peculiarities in the target system's architecture prevent the effective use of higher-level languages.<ref name="Provinciano_2005"/>

Assemblers with a strong macro engine allow structured programming via macros, such as the switch macro provided with the Masm32 package (this code is a complete program):

<syntaxhighlight lang="nasm">
include \masm32\include\masm32rt.inc	; use the Masm32 library

.code
demomain:
  REPEAT 20
	switch rv(nrandom, 9)	; generate a number between 0 and 8
	mov ecx, 7
	case 0
		print "case 0"
	case ecx				; in contrast to most other programming languages,
		print "case 7"		; the Masm32 switch allows "variable cases"
	case 1 .. 3
		.if eax==1
			print "case 1"
		.elseif eax==2
			print "case 2"
		.else
			print "cases 1 to 3: other"
		.endif
	case 4, 6, 8
		print "cases 4, 6 or 8"
	default
		mov ebx, 19		     ; print 20 stars
		.Repeat
			print "*"
			dec ebx
		.Until Sign?		 ; loop until the sign flag is set
	endsw
	print chr$(13, 10)
  ENDM
  exit
end demomain
</syntaxhighlight>

==Use of assembly language==
When the [[stored-program computer]] was introduced, programs were written in machine code, and loaded into the computer from punched paper tape or toggled directly into memory from console switches.{{citation needed|date=August 2024}} [[Kathleen Booth]] "is credited with inventing assembly language"<ref name="Dufresne_2018"/><ref name="Booth_1947"/> based on theoretical work she began in 1947, while working on the [[APEXC|ARC2]] at [[Birkbeck, University of London]], following consultation by [[Andrew Donald Booth|Andrew Booth]] (later her husband) with mathematician [[John von Neumann]] and physicist [[Herman Goldstine]] at the [[Institute for Advanced Study]].<ref name="Booth_1947"/><ref name="Campbell-Kelly_1982"/>

In late 1948, the [[EDSAC|Electronic Delay Storage Automatic Calculator]] (EDSAC) had an assembler (named "initial orders") integrated into its [[booting|bootstrap]] program. It used one-letter mnemonics developed by [[David Wheeler (computer scientist)|David Wheeler]], who is credited by the IEEE Computer Society as the creator of the first "assembler".<ref name="Salomon_1992"/><ref name="Campbell-Kelly_1980"/><ref name="Wheeler_1985"/> Reports on the EDSAC introduced the term "assembly" for the process of combining fields into an instruction word.<ref name="Wilkes_1949"/> SOAP ([[Symbolic Optimal Assembly Program]]) was an assembly language for the [[IBM 650]] computer written by Stan Poley in 1955.<ref name="Cruz_2019"/>

Assembly languages eliminated much of the error-prone, tedious, and time-consuming [[first-generation language|first-generation]] programming needed with the earliest computers, freeing programmers from tedium such as remembering numeric codes and calculating addresses. They were once widely used for all sorts of programming. By the late 1950s their use had largely been supplanted by higher-level languages in the search for improved [[programming productivity]].<ref>{{Cite magazine |last=Abell |first=John C. |title=Oct. 15, 1956: Fortran Forever Changes Computing's Fortunes |url=https://www.wired.com/2009/10/1015fortran-launch/ |access-date=2024-03-02 |magazine=Wired |language=en-US |issn=1059-1028}}</ref> Today, assembly language is still used for direct hardware manipulation, access to specialized processor instructions, or to address critical performance issues.<ref>{{cite journal|title=The Origins of Informatics|last=Collen|first=Morris F.|journal=[[Journal of the American Medical Informatics Association]]|date=March–April 1994|volume=1|issue=2|pages=96–97|doi=10.1136/jamia.1994.95236152| pmid=7719803 | pmc=116189 }}</ref> Typical uses are [[device driver]]s, low-level [[embedded system]]s, and [[real-time computing|real-time]] systems (see {{section link|#Current usage}}).

Numerous programs were written entirely in assembly language. The [[Burroughs MCP]] (1961) was the first computer for which an operating system was not developed entirely in assembly language; it was written in [[Executive Systems Problem Oriented Language]] (ESPOL), an Algol dialect. Many commercial applications were written in assembly language as well, including a large amount of the [[IBM mainframe]] software developed by large corporations. [[COBOL]], [[FORTRAN]] and some PL/I eventually displaced assembly language, although a number of large organizations retained assembly-language application infrastructures well into the 1990s.

Assembly language was the primary development language for 8-bit home computers such as the [[Apple II]], [[Atari 8-bit computers]], [[ZX Spectrum]], and [[Commodore 64]]. [[Interpreter (computing)|Interpreted]] [[BASIC]] on these systems did not offer maximum execution speed and full use of facilities to take full advantage of the available hardware. Assembly language was the default choice for programming 8-bit consoles such as the [[Atari 2600]] and [[Nintendo Entertainment System]].

Key software for [[IBM PC compatible]]s such as [[MS-DOS]], [[Turbo Pascal]], and the [[Lotus 1-2-3]] spreadsheet was written in assembly language. As computer speed grew exponentially, assembly language became a tool for speeding up parts of programs, such as the rendering of ''[[Doom (1993 video game)|Doom]]'', rather than a dominant development language. In the 1990s, assembly language was used to maximise performance from systems such as the [[Sega Saturn]],<ref name="Pettus_2008"/> and as the primary language for arcade hardware using the [[TMS34010]] integrated CPU/GPU such as ''[[Mortal Kombat (1992 video game)|Mortal Kombat]]'' and ''[[NBA Jam (1993 video game)|NBA Jam]]''.

===Current usage===
There has been debate over the usefulness and performance of assembly language relative to high-level languages.<ref name="Kauler_1997" />

Although assembly language has specific niche uses where it is important (see below), there are other tools for optimization.<ref name="Hsieh_2020"/>

{{As of|2017|07}}, the [[TIOBE index]] of programming language popularity ranks assembly language at 11, ahead of [[Visual Basic]], for example.<ref name="tiobe"/> Assembler can be used to optimize for speed or optimize for size. In the case of speed optimization, modern [[optimizing compiler]]s are claimed<ref name="Rusling_2012"/> to render high-level languages into code that can run as fast as hand-written assembly, despite some counter-examples.<ref name="Markoff_2005"/><ref name="bit-field"/><ref name="gcc-mess"/> The complexity of modern processors and memory sub-systems makes effective optimization increasingly difficult for compilers and assembly programmers alike.<ref name="Hyde_2008"/><ref name="compiler-fails1"/> Increasing processor performance has meant that most CPUs sit idle most of the time,<ref name="Click_2014"/> with delays caused by predictable bottlenecks such as cache misses, [[Input/output|I/O]] operations and [[Memory paging|paging]], making raw code execution speed a non-issue for many programmers.

There are still certain computer programming domains in which the use of assembly programming is more common:

* Writing code for systems with {{Clarify|date=June 2021|reason=Does this refer only to microprocessors or also to midrange and mainframe systems?|text=older processors}} that have limited high-level language options such as the [[Atari 2600]], [[Commodore 64]], and [[graphing calculator]]s.<ref name="Fargo_2008"/> Programs for these computers of the 1970s and 1980s are often written in the context of [[demoscene]] or [[retrogaming]] subcultures.
* Code that must interact directly with the hardware, for example in [[device driver]]s and [[interrupt handler]]s.
* In an embedded processor or [[Digital Signal Processor|DSP]], high-repetition interrupts require the shortest number of cycles per interrupt, such as an interrupt that occurs 1000 or 10000 times a second.
* Programs that need to use processor-specific instructions not implemented in a compiler. A common example is the [[circular shift|bitwise rotation]] instruction at the core of many encryption algorithms, as well as querying the parity of a byte or the 4-bit carry of an addition.
* Stand-alone executables that are required to execute without recourse to the [[run-time system|run-time]] components or [[library (computing)|libraries]] associated with a high-level language, such as the firmware for telephones, automobile fuel and ignition systems, air-conditioning control systems, and security systems.
* Programs with performance-sensitive inner loops, where assembly language provides optimization opportunities that are difficult to achieve in a high-level language. For example, [[linear algebra]] with [[Basic Linear Algebra Subprograms|BLAS]]<ref name="Markoff_2005"/><ref name="BLAS_2008"/> or [[discrete cosine transform]]ation (e.g. [[Single instruction, multiple data|SIMD]] assembly version from [[x264]]<ref name="Videolan_2010"/>).
* Programs that create vectorized functions for programs in higher-level languages such as C.  In the higher-level language this is sometimes aided by compiler [[intrinsic function]]s which map directly to SIMD mnemonics, but nevertheless result in a one-to-one assembly conversion specific for the given vector processor.
* [[Real-time computing|Real-time]] programs such as simulations, flight navigation systems, and medical equipment. For example, in a [[fly-by-wire]] system, telemetry must be interpreted and acted upon within strict time constraints. Such systems must eliminate sources of unpredictable delays, which may be created by interpreted languages, automatic [[garbage collection (computer science)|garbage collection]], paging operations, or [[preemptive multitasking]]. Choosing assembly or [[low-level programming language|lower-level languages]] for such systems gives programmers greater visibility and control over processing details.
* Cryptographic algorithms that must always take strictly the same time to execute, preventing [[timing attack]]s.
* Video encoders and decoders such as rav1e (an encoder for [[AV1]])<ref>{{cite web |url=https://github.com/xiph/rav1e/blob/v0.6.3/README.md#features-1= |title=rav1e/README.md at v0.6.3 |website=[[GitHub]] |access-date=21 February 2023 |archive-date=22 February 2023 |archive-url=https://web.archive.org/web/20230222005925/https://github.com/xiph/rav1e/blob/v0.6.3/README.md |url-status=live}}</ref> and dav1d (the reference decoder for AV1)<ref>{{cite web |url=https://code.videolan.org/videolan/dav1d/-/blob/1.1.0/README.md |title=README.md · 1.1.0 · VideoLAN / dav1d |date=13 February 2023 |access-date=21 February 2023 |archive-date=22 February 2023 |archive-url=https://web.archive.org/web/20230222004317/https://code.videolan.org/videolan/dav1d/-/blob/1.1.0/README.md |url-status=live}}</ref> contain assembly to leverage [[AVX2]] and [[Neon (instruction set)|ARM Neon]] instructions when available.
* Modify and extend legacy code written for [[IBM mainframe]] computers.<ref name="Bosworth_2016"/><ref>{{cite web |url=https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sc236852/$file/idad500_v2r3.pdf |title=z/OS Version 2 Release 3 DFSMS Macro Instructions for Data Sets |publisher=IBM |date=15 February 2019 |access-date=14 September 2021 |url-status=live|archive-url=https://web.archive.org/web/20210625140314/https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sc236852/$file/idad500_v2r3.pdf |archive-date=25 June 2021 }}</ref>
* Situations where complete control over the environment is required, in extremely high-security situations where [[Trusting trust#Reflections on Trusting Trust|nothing can be taken for granted]].
* [[Computer virus]]es, [[bootloader]]s, certain [[device driver]]s, or other items very close to the hardware or low-level operating system.
* [[Instruction set simulator]]s for monitoring, tracing and [[debugging]] where additional overhead is kept to a minimum.
* Situations where no high-level language exists, on a new or specialized processor for which no [[cross compiler]] is available.
* [[Reverse engineering]] and modifying program files such as:
** existing [[binary file|binaries]] that may or may not have originally been written in a high-level language, for example when trying to recreate programs for which source code is not available or has been lost, or cracking copy protection of proprietary software.
** [[Video game]]s (also termed [[ROM hacking]]), which is possible via several methods. The most widely employed method is altering program code at the assembly language level.

Assembly language is still taught in most [[computer science]] and [[electronic engineering]] programs. Although few programmers today regularly work with assembly language as a tool, the underlying concepts remain important. Such fundamental topics as [[binary arithmetic]], [[memory management|memory allocation]], [[Stack (abstract data type)|stack processing]], [[character set]] encoding, [[interrupt]] processing, and [[compiler]] design would be hard to study in detail without a grasp of how a computer operates at the hardware level. Since a computer's behaviour is fundamentally defined by its instruction set, the logical way to learn such concepts is to study an assembly language. Most modern computers have similar instruction sets. Therefore, studying a single assembly language is sufficient to learn the basic concepts, recognize situations where the use of assembly language might be appropriate, and to see how efficient executable code can be created from high-level languages.<ref name="Hyde_2003"/>

===Typical applications===
* Assembly language is typically used in a system's [[booting|boot]] code, the low-level code that initializes and tests the system hardware prior to booting the operating system and is often stored in [[read-only memory|ROM]]. ([[BIOS]] on [[IBM-compatible PC]] systems and [[CP/M]] is an example.)
* Assembly language is often used for low-level code, for instance for [[operating system kernel]]s, which cannot rely on the availability of pre-existing system calls and must indeed implement them for the particular processor architecture on which the system will be running.
* Some compilers translate high-level languages into assembly first before fully compiling, allowing the assembly code to be viewed for [[debugging]] and optimization purposes.
* Some compilers for relatively low-level languages, such as [[Pascal (programming language)|Pascal]] or [[C (programming language)|C]], allow the programmer to embed assembly language directly in the source code (so called [[inline assembly]]). Programs using such facilities can then construct abstractions using different assembly language on each hardware platform. The system's [[software portability|portable code]] can then use these processor-specific components through a uniform interface.
* Assembly language is useful in [[reverse engineering]]. Many programs are distributed only in machine code form which is straightforward to translate into assembly language by a [[disassembler]], but more difficult to translate into a higher-level language through a [[decompiler]]. Tools such as the [[Interactive Disassembler]] make extensive use of disassembly for such a purpose. This technique is used by hackers to crack commercial software, and competitors to produce software with similar results from competing companies.
* Assembly language is used to enhance speed of execution, especially in early personal computers with limited processing power and RAM.
* Assemblers can be used to generate blocks of data, with no high-level language overhead, from formatted and commented source code, to be used by other code.<ref name="Paul_2001_NECPINW"/><ref name="Paul_2002_CPI"/>

==See also==
{{Portal|Computer programming}}
* {{Annotated link|[[Compiler]]}}
* {{Annotated link|[[Comparison of assemblers]]}}
* {{Annotated link|[[Disassembler]]}}
* {{Annotated link|[[Hexadecimal]]}}
* {{Annotated link|[[Information Processing Language]]}}
* {{Annotated link|[[Instruction set architecture]]}}
* {{Annotated link|[[Little man computer]]}}
* {{Annotated link|[[Nibble]]}}
* {{Annotated link|[[Typed assembly language]]}}

==Notes==
{{Reflist|group="nb"|refs=
<ref group="nb" name="NB1">AMD manufactured second-source Intel 8086, 8088, and 80286 CPUs, and perhaps 8080A and 8085A CPUs, under license from Intel, but starting with the 80386, Intel refused to share their x86 CPU designs with anyone&mdash;AMD sued about this for breach of contract&mdash;and AMD designed, made, and sold 32-bit and 64-bit x86-family CPUs without Intel's help or endorsement.</ref>
<ref group="nb" name="NB3">This is one of two redundant forms of this instruction that operate identically. The 8086 and several other CPUs from the late 1970s/early 1980s have redundancies in their instruction sets, because it was simpler for engineers to design these CPUs (to fit on silicon chips of limited sizes) with the redundant codes than to eliminate them (see [[don't-care term]]s). Each assembler will typically generate only one of two or more redundant instruction encodings, but a ''disassembler'' will usually recognize any of them.</ref>
<ref group="nb" name="NB4">In 7070 Autocoder, a macro definition is a 7070 macro generator program that the assembler calls; Autocoder provides special macros for macro generators to use.</ref>
}}

==References==
{{Reflist|refs=
<ref name="IBM_2014_ASM">{{cite book
 |title=High Level Assembler for z/OS & z/VM & z/VSE Language Reference Version 1 Release 6
 |id=SC26-4940-06 
 |section=Assembler language
 |section-url=https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.asma400/asmr102112.htm
 |url=https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.asma400/toc.htm
 |date=2014 |orig-year=1990 |publisher=[[IBM]]
 }}</ref>
<ref name="Kornelis_2010">{{cite web |title=High Level Assembler – Opcodes overview, Assembler Directives |author-first=A. F. |author-last=Kornelis |date=2010 |orig-year=2003 |url=http://www.bixoft.nl/english/opcd00.htm |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324151326/http://www.bixoft.nl/english/opcd00.htm |archive-date=2020-03-24}}</ref>
<ref name="IBM_2014_Macro">{{cite book
 |title=High Level Assembler for z/OS & z/VM & z/VSE Language Reference Version 1 Release 6
 |id=SC26-4940-06 
 |section=Macro instructions
 |section-url=https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.asma400/asmr102115.htm
 |url=https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.asma400/toc.htm
|publisher=[[IBM]] |date=2014 |orig-year=1990 
 }}</ref>
<ref name="Wilkes_1951">{{cite book |author-last1=Wilkes |author-first1=Maurice Vincent |author-link1=Maurice Vincent Wilkes |author-last2=Wheeler |author-first2=David John |author-link2=David John Wheeler |author-last3=Gill |author-first3=Stanley J. |author-link3=Stanley J. Gill |title=The preparation of programs for an electronic digital computer |date=1951 |publisher=[[Tomash Publishers]] |isbn=978-0-93822803-5 |oclc=313593586 |edition=Reprint 1982 }}</ref>
<ref name="Fairhead_2017">{{cite web |author-last=Fairhead |author-first=Harry |title=History of Computer Languages - The Classical Decade, 1950s |work=I Programmer |date=2017-11-16 |url=https://www.i-programmer.info/history/57-computer-languages/471-the-classical-decade.html |access-date=2020-03-06 |url-status=dead |archive-url=https://web.archive.org/web/20200102192823/https://www.i-programmer.info/history/57-computer-languages/471-the-classical-decade.html |archive-date=2020-01-02}}</ref>
<ref name="OS360_2011">{{cite web |title=How do assembly languages depend on operating systems? |date=2011-07-28 |work=Stack Exchange |publisher=[[Stack Exchange Inc.]] |url=https://stackoverflow.com/questions/6859348/how-do-assembly-languages-depend-on-operating-systems |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324152747/https://stackoverflow.com/questions/6859348/how-do-assembly-languages-depend-on-operating-systems |archive-date=2020-03-24}} (NB. System calls often vary, e.g. for [[OS/360 and successors|MVS]] vs. [[DOS/360 and successors|VSE]] vs. VM/CMS; the binary/executable formats for different operating systems may also vary.)</ref>
<ref name="Salomon_1992">{{cite book |author-first=David |author-last=Salomon |editor-first=Ian D. |editor-last=Chivers |title=Assemblers and Loaders |date=February 1993 |pages=7, 237–238 |orig-year=1992 |edition=1 |series=Ellis Horwood Series In Computers And Their Applications |publisher=[[Ellis Horwood Limited]] / [[Simon & Schuster International Group]] |location=California State University, Northridge, California, US |publication-place=Chicester, West Sussex, UK |isbn=0-13-052564-2 |url=http://www.davidsalomon.name/assem.advertis/asl.pdf |access-date=2008-10-01 |url-status=live |archive-url=https://web.archive.org/web/20200323010358/http://www.davidsalomon.name/assem.advertis/asl.pdf |archive-date=2020-03-23}} (xiv+294+4 pages)</ref>
<ref name="Saxon_1962">{{cite book |author-first1=James A. |author-last1=Saxon |author-first2=William S. |author-last2=Plette |title=Programming the IBM 1401, a self-instructional programmed manual |location=Englewood Cliffs, New Jersey, US |publisher=[[Prentice-Hall]] |date=1962 |lccn=62-20615 |url=https://babel.hathitrust.org/cgi/pt?id=mdp.39015000480718;view=2up;seq=6}} (NB. Use of the term ''assembly program''.)</ref>
<ref name="Ohio_2016">{{cite web |title=Assembly: Review |volume=Lecture 14 |series=Computer Science and Engineering |publisher=College of Engineering,  [[Ohio State University]]<!--Wikipedians do not use "The" as part of Ohio State's name; it is considered a marketing gimmick, and routinely deleted.--> |date=2016 |url=http://web.cse.ohio-state.edu/~sivilotti.1/teaching/3903.recent/lectures/lecture14.pdf |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324153925/http://web.cse.ohio-state.edu/~sivilotti.1/teaching/3903.recent/lectures/lecture14.pdf |archive-date=2020-03-24}}</ref>
<ref name="Archer_2016">{{cite book |title=Assembly Language For Students |url=https://dl.acm.org/citation.cfm?id=3125846 |author-first=Benjamin |author-last=Archer |date=November 2016 |publisher=[[CreateSpace Independent Publishing]] |location=North Charleston, South Carolina, US |isbn=978-1-5403-7071-6 |quote=Assembly language may also be called symbolic machine code.}}</ref>
<ref name="Bosworth_2016">{{cite web |author-first=Edward |author-last=Bosworth |date=2016 |title=Chapter 1 – Why Study Assembly Language |website=www.edwardbosworth.com |url=http://www.edwardbosworth.com/My3121Textbook_HTM/MyText3121_Ch01_V01.htm |access-date=2016-06-01 |url-status=live |archive-url=https://web.archive.org/web/20200324154257/http://www.edwardbosworth.com/My3121Textbook_HTM/MyText3121_Ch01_V01.htm |archive-date=2020-03-24}}</ref>
<ref name="Hyde_2003">{{cite book |author-first=Randall |author-last=Hyde |author-link=Randall Hyde |title=The Art of Assembly Language |publisher=[[No Starch Press]] |edition=2 |date=September 2003 |orig-year=1996-09-30 |isbn=1-886411-97-2 |chapter=Foreword ("Why would anyone learn this stuff?") / Chapter 12 – Classes and Objects |url=http://www.nostarch.com:80/frameset.php?startat=assembly |url-status=dead |archive-url=https://web.archive.org/web/20100506233612/http://www.nostarch.com/frameset.php?startat=assembly |archive-date=6 May 2010 |access-date=22 June 2020 }} Errata: [https://web.archive.org/web/20200323150730/http://www.plantation-productions.com/Webster/www.artofasm.com/AoAErrata.html] (928 pages) [https://web.archive.org/web/20200323151406/http://www.plantation-productions.com/Webster/www.artofasm.com/index.html][https://web.archive.org/web/20090720021936/http://www.arl.wustl.edu/~lockwood/class/cs306/books/artofasm/toc.html]</ref>
<ref name="Daintith_2019">{{cite web |editor-first=John |editor-last=Daintith |work=A Dictionary of Computing |title=meta-assembler |date=2019 |url=http://www.encyclopedia.com/doc/1O11-metaassembler.html |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324154503/https://www.encyclopedia.com/computing/dictionaries-thesauruses-pictures-and-press-releases/meta-assembler |archive-date=2020-03-24}}</ref>
<ref name="Beck_1996">{{cite book |author-last=Beck |author-first=Leland L. |title=System Software: An Introduction to Systems Programming |publisher=[[Addison Wesley]] |date=1996 |chapter=2}}</ref>
<ref name="Intel_1999">{{cite book |title=Intel Architecture Software Developer's Manual, Volume 2: Instruction Set Reference |date=1999 |volume=2 |publisher=[[Intel Corporation]] |url=http://download.intel.com/design/PentiumII/manuals/24319102.PDF |access-date=2010-11-18 |url-status=dead |archive-url=https://web.archive.org/web/20090611193346/http://download.intel.com/design/PentiumII/manuals/24319102.PDF |archive-date=11 June 2009 }}</ref>
<ref name="Evans_2006">{{cite web |editor-last=Evans |editor-first=David |author-first1=Adam |author-last1=Ferrari |author-first2=Alan |author-last2=Batson |author-first3=Mike |author-last3=Lack |author-first4=Anita |author-last4=Jones |title=x86 Assembly Guide |date=2018-11-19 |orig-year=Spring 2006 |publisher=[[University of Virginia]] |series=Computer Science CS216: Program and Data Representation |url=http://www.cs.virginia.edu/~evans/cs216/guides/x86.html |access-date=2010-11-18 |url-status=live |archive-url=https://web.archive.org/web/20200324154938/http://www.cs.virginia.edu/~evans/cs216/guides/x86.html |archive-date=2020-03-24}}</ref>
<ref name="SPARC_1992">{{cite web |publisher=[[SPARC International]] |title=The SPARC Architecture Manual, Version 8 |date=1992 |url=http://www.sparc.com/standards/V8.pdf |access-date=2011-12-10 |url-status=dead |archive-url=https://web.archive.org/web/20111210201410/http://www.sparc.com/standards/V8.pdf |archive-date=2011-12-10}}</ref>
<ref name="Moxham_1996">{{cite web |author-first=James |author-last=Moxham |date=1996 |title=ZINT Z80 Interpreter |work=Z80 Op Codes for ZINT |url=http://www.z80.de/z80/z80code.htm |access-date=2013-07-21 |url-status=live |archive-url=https://web.archive.org/web/20200324155515/http://www.z80.de/z80/z80code.htm |archive-date=2020-03-24}}</ref>
<ref name="Hyde_MASM">{{cite book |author-first=Randall |author-last=Hyde |author-link=Randall Hyde |title=The Art of Computer Programming |chapter=Chapter 8. MASM: Directives & Pseudo-Opcodes |chapter-url=http://flint.cs.yale.edu/cs422/doc/art-of-asm/pdf/CH08.PDF |access-date=2011-03-19 |url-status=live |archive-url=https://web.archive.org/web/20200324155843/https://www.cs.yale.edu/flint/cs422/doc/art-of-asm/pdf/CH08.PDF |archive-date=2020-03-24}}</ref>
<ref name="Autocoder">{{cite book |title=1401 Autocoder System, Program #1401-AU-037, Version 3, Modification Level 11 |url=http://vandyke.mynetgear.com/1401/progs/autocoder/mod.11.pdf |date=December 7, 1965 |quote=The following minor restriction or limitation is in effect with regard to the use of 1401 Autocoder when coding macro instructions ... |access-date=2024-01-21}}</ref>
<ref name="Griswold_1972">{{cite book |author-last=Griswold |author-first=Ralph E. |author-link=Ralph E. Griswold |title=The Macro Implementation of SNOBOL4 |chapter=Chapter 1 |location=San Francisco, California, US |publisher=[[W. H. Freeman and Company]] |date=1972 |isbn=0-7167-0447-1}}</ref>
<ref name="Microsoft_2012_Macros">{{cite web |title=Macros (C/C++), MSDN Library for Visual Studio 2008 |publisher=[[Microsoft Corp.]] |date=2012-11-16 |url=http://msdn.microsoft.com/en-us/library/503x3e3s%28v=VS.90%29.aspx |access-date=2010-06-22 |url-status=live |archive-url=https://web.archive.org/web/20200324160251/https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/503x3e3s(v=vs.90)?redirectedfrom=MSDN |archive-date=2020-03-24}}</ref>
<ref name="Kessler_1970">{{cite web |author-first=Marvin M. |author-last=Kessler |title=*Concept* Report 14 - Implementation of Macros To Permit Structured Programming in OS/360 |publisher=[[International Business Machines Corporation]] |location=Gaithersburg, Maryland, US |date=1970-12-18 |work=MVS Software: Concept 14 Macros |url=http://skycoast.us/pscott/software/mvs/concept14.html |access-date=2009-05-25 |url-status=live |archive-url=https://web.archive.org/web/20200324160528/http://skycoast.us/pscott/software/mvs/concept14.html |archive-date=2020-03-24}}</ref>
<ref name="assembly-language?cat=technology">{{cite web |title=assembly language: Definition and Much More from Answers.com |website=answers.com |url=http://www.answers.com/topic/assembly-language?cat=technology |access-date=2008-06-19 |url-status=dead |archive-url=https://web.archive.org/web/20090608215406/http://www.answers.com/topic/assembly-language?cat=technology |archive-date=8 June 2009 }}</ref>
<ref name="Provinciano_2005">{{cite web |author-last=Provinciano |author-first=Brian |title=NESHLA: The High Level, Open Source, 6502 Assembler for the Nintendo Entertainment System |date=2005-04-17 |url=https://neshla.sourceforge.net/ |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324161216/http://neshla.sourceforge.net/ |archive-date=2020-03-24}}</ref>
<ref name="Dufresne_2018">{{cite web |author-first=Steven |author-last=Dufresne |date=2018-08-21 |title=Kathleen Booth: Assembling Early Computers While Inventing Assembly |url=https://hackaday.com/2018/08/21/kathleen-booth-assembling-early-computers-while-inventing-assembly |access-date=2019-02-10 |url-status=live |archive-url=https://web.archive.org/web/20200324150537/https://hackaday.com/2018/08/21/kathleen-booth-assembling-early-computers-while-inventing-assembly/ |archive-date=2020-03-24}}</ref>
<ref name="Booth_1947">{{cite book |author-first1=Andrew Donald |author-last1=Booth  |author-link1=Andrew Donald Booth |author-first2=Kathleen Hylda Valerie |author-last2=Britten |author-link2=Kathleen Hylda Valerie Britten |title=General considerations in the design of an all purpose electronic digital computer<!-- (Coding for the ARC) --> |edition=2 |location=The Institute for Advanced Study, Princeton, New Jersey, US |publisher=[[Birkbeck College, London]] |date=September 1947 |orig-year=August 1947 |url=http://mt-archive.info/Booth-1947.pdf |access-date=2019-02-10 |url-status=live |archive-url=https://web.archive.org/web/20200324161441/http://mt-archive.info/Booth-1947.pdf |archive-date=2020-03-24 |quote=The non-original ideas, contained in the following text, have been derived from a number of sources, ... It is felt, however, that acknowledgement should be made to Prof. John von Neumann and to Dr. Herman Goldstein for many fruitful discussions ...}}</ref>
<ref name="Campbell-Kelly_1982">{{cite journal |author-last=Campbell-Kelly |author-first=Martin |author-link=Martin Campbell-Kelly |title=The Development of Computer Programming in Britain (1945 to 1955) |journal=[[IEEE Annals of the History of Computing]] |date=April 1982 |volume=4 |issue=2 |pages=121–139 |doi=10.1109/MAHC.1982.10016|s2cid=14861159 }}</ref> 
<ref name="Campbell-Kelly_1980">{{cite journal |author-first=Martin |author-last=Campbell-Kelly |author-link=Martin Campbell-Kelly |title=Programming the EDSAC: Early Programming Activity at the University of Cambridge |journal=[[IEEE Annals of the History of Computing]] |date=1980 |volume=2 |number=1 |pages=7–36 |doi=10.1109/MAHC.1980.10009}}</ref>
<ref name="Wheeler_1985">{{cite web |title=1985 Computer Pioneer Award 'For assembly language programming' David Wheeler |date=27 March 2018 |url=https://www.computer.org/web/awards/pioneer-david-wheeler}}</ref>
<ref name="Wilkes_1949">{{cite journal |author-first=Maurice Vincent |author-last=Wilkes |author-link=Maurice Vincent Wilkes |title=The EDSAC – an Electronic Calculating Machine |journal=Journal of Scientific Instruments |date=1949 |volume=26 |issue=12 |pages=385–391 |doi=10.1088/0950-7671/26/12/301|bibcode=1949JScI...26..385W }}</ref>
<ref name="Cruz_2019">{{cite web |title=The IBM 650 Magnetic Drum Calculator |author-first=Frank |author-last=da Cruz |date=2019-05-17 |publisher=[[Columbia University]] |series=Computing History - A Chronology of Computing |url=http://www.columbia.edu/cu/computinghistory/650.html |access-date=2012-01-17 |url-status=live |archive-url=https://web.archive.org/web/20200215063114/http://www.columbia.edu/cu/computinghistory/index.html |archive-date=2020-02-15}}</ref>
<ref name="Pettus_2008">{{cite web |author-first=Sam |author-last=Pettus |title=SegaBase Volume 6 - Saturn |date=2008-01-10 |url=http://www.eidolons-inn.net/tiki-index.php?page=SegaBase+Saturn |access-date=2008-07-25 |url-status=usurped |archive-url=https://web.archive.org/web/20080713074116/http://www.eidolons-inn.net/tiki-index.php?page=SegaBase+Saturn |archive-date=2008-07-13}}</ref>
<ref name="Kauler_1997">{{cite book |title=Windows Assembly Language and Systems Programming: 16- and 32-Bit Low-Level Programming for the PC and Windows |publisher=[[CRC Press]] |isbn=978-1-48227572-8 |author-first=Barry |author-last=Kauler |date=1997-01-09 |url=https://books.google.com/books?id=E0dZDwAAQBAJ |access-date=2020-03-24 |quote=Always the debate rages about the applicability of assembly language in our modern programming world.}}</ref>
<ref name="Hsieh_2020">{{cite web |title=Programming Optimization |author-first=Paul |author-last=Hsieh |date=2020-03-24 |orig-year=2016, 1996 |url=http://www.azillionmonkeys.com/qed/optimize.html<!-- http://icps.u-strasbg.fr/~bastoul/local_copies/hsieh.html --> |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324163624/http://www.azillionmonkeys.com/qed/optimize.html<!-- https://web.archive.org/web/20200324163339/http://icps.u-strasbg.fr/~bastoul/local_copies/hsieh.html --> |archive-date=2020-03-24 |quote=... design changes tend to affect performance more than ... one should not skip straight to assembly language until ...}}</ref>
<ref name="tiobe">{{cite news |title=TIOBE Index |publisher=[[TIOBE Software]] |url=http://www.tiobe.com/tiobe_index |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324163848/https://www.tiobe.com/tiobe-index/ |archive-date=2020-03-24}}</ref>
<ref name="Rusling_2012">{{cite web |author-last=Rusling |author-first=David A. |work=The Linux Kernel |title=Chapter 2 Software Basics |date=1999 |orig-year=1996 |url=http://tldp.org/LDP/tlk/basics/sw.html |access-date=2012-03-11 |url-status=live |archive-url=https://web.archive.org/web/20200324164120/http://tldp.org/LDP/tlk/basics/sw.html |archive-date=2020-03-24}}</ref>
<ref name="Markoff_2005">{{cite news |title=Writing the Fastest Code, by Hand, for Fun: A Human Computer Keeps Speeding Up Chips |newspaper=[[The New York Times]] |author-first=John Gregory |author-last=Markoff |author-link=John Gregory Markoff |date=2005-11-28 |location=Seattle, Washington, US |url=https://www.nytimes.com/2005/11/28/technology/28super.html?_r=1 |access-date=2010-03-04 |url-status=live |archive-url=https://web.archive.org/web/20200323163333/https://www.nytimes.com/2005/11/28/technology/writing-the-fastest-code-by-hand-for-fun-a-human-computer-keeps.html |archive-date=2020-03-23}}</ref>
<ref name="bit-field">{{cite web |title=Bit-field-badness |website=hardwarebug.org |date=2010-01-30 |url=http://hardwarebug.org/2010/01/30/bit-field-badness/ |access-date=2010-03-04 |url-status=dead |archive-url=https://web.archive.org/web/20100205120952/http://hardwarebug.org/2010/01/30/bit-field-badness/ |archive-date=2010-02-05}}</ref>
<ref name="gcc-mess">{{cite web |title=GCC makes a mess |website=hardwarebug.org |date=2009-05-13 |url=http://hardwarebug.org/2009/05/13/gcc-makes-a-mess/ |access-date=2010-03-04 |url-status=dead |archive-url=https://web.archive.org/web/20100316212040/http://hardwarebug.org/2009/05/13/gcc-makes-a-mess/ |archive-date=2010-03-16}}</ref>
<ref name="Hyde_2008">{{cite web |title=The Great Debate |access-date=2008-07-03 |author-first=Randall |author-last=Hyde |author-link=Randall Hyde |url=http://webster.cs.ucr.edu/Page_TechDocs/GreatDebate/debate1.html |url-status=dead |archive-url=https://web.archive.org/web/20080616110102/http://webster.cs.ucr.edu/Page_TechDocs/GreatDebate/debate1.html |archive-date=2008-06-16}}</ref>
<ref name="compiler-fails1">{{cite web |title=Code sourcery fails again |website=hardwarebug.org |date=2010-01-30 |url=http://hardwarebug.org/2008/11/28/codesourcery-fails-again/ |access-date=2010-03-04 |url-status=dead |archive-url=https://web.archive.org/web/20100402221204/http://hardwarebug.org/2008/11/28/codesourcery-fails-again/ |archive-date=2010-04-02}}</ref>
<ref name="Click_2014">{{cite web |author-last1=Click |author-first1=Cliff |author-first2=Brian |author-last2=Goetz |title=A Crash Course in Modern Hardware |url=http://www.infoq.com/presentations/click-crash-course-modern-hardware |access-date=2014-05-01 |url-status=live |archive-url=https://web.archive.org/web/20200324164402/https://www.infoq.com/presentations/click-crash-course-modern-hardware/ |archive-date=2020-03-24}}</ref>
<ref name="Fargo_2008">{{cite web |title=68K Programming in Fargo II |url=http://tifreakware.net/tutorials/89/a/calc/fargoii.htm |access-date=2008-07-03 |url-status=live |archive-url=https://web.archive.org/web/20080702181616/http://tifreakware.net/tutorials/89/a/calc/fargoii.htm |archive-date=2008-07-02}}</ref>
<ref name="BLAS_2008">{{cite web |title=BLAS Benchmark-August2008 |publisher=eigen.tuxfamily.org |date=2008-08-01 |url=http://eigen.tuxfamily.org/index.php?title=Benchmark-August2008 |access-date=2010-03-04 |url-status=live |archive-url=https://web.archive.org/web/20200324164844/http://eigen.tuxfamily.org/index.php?title=Benchmark-August2008 |archive-date=2020-03-24}}</ref>
<ref name="Videolan_2010">{{cite web |title=x264.git/common/x86/dct-32.asm |publisher=git.videolan.org |date=2010-09-29 |url=http://git.videolan.org/?p=x264.git;a=tree;f=common/x86;hb=HEAD |access-date=2010-09-29 |url-status=dead |archive-url=https://web.archive.org/web/20120304083653/http://git.videolan.org/?p=x264.git%3Ba%3Dtree%3Bf%3Dcommon%2Fx86%3Bhb%3DHEAD |archive-date=2012-03-04}}</ref>
<ref name="Paul_2001_NECPINW">{{citation |title=Specification and reference documentation for NECPINW |edition=2.08<!-- Newer 3.xx revisions exist as well --> |work=NECPINW.CPI - DOS code page switching driver for [[NEC Pinwriter]]s |at=FILESPEC.TXT, NECPINW.ASM, EUROFONT.INC from NECPI208.ZIP |author-first=Matthias R. |author-last=Paul |date=2001 |orig-year=1996 |url=http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/print/cpi/NECPI208.ZIP<!-- http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/print/cpi/ --> |access-date=2013-04-22 |url-status=live |archive-url=https://web.archive.org/web/20170910202610/http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/print/cpi/NECPI208.ZIP |archive-date=2017-09-10}}<!-- https://web.archive.org/web/20090215001349/http://www.uni-bonn.de:80/~uzs180/mpdokeng.html#M.NECPINW --></ref>
<ref name="Paul_2002_CPI">{{cite web |title=[fd-dev] mkeyb |author-first=Matthias R. |author-last=Paul |date=2002-05-13 |work=freedos-dev |url=https://marc.info/?l=freedos-dev&m=102133580113139&w=2 |access-date=2018-09-10 |url-status=live |archive-url=https://archive.today/20180910213410/https://marc.info/?l=freedos-dev&m=102133580113139&w=2 |archive-date=2018-09-10}}</ref>
<ref name="Brooks_1986_NSB">{{cite conference |title = No Silver Bullet—Essence and Accident in Software Engineering | last = Brooks |first = Frederick P. |author-link = Fred Brooks |book-title = Proceedings of the IFIP Tenth World Computing Conference|pages = 1069–1076 |year = 1986 |ref = Brooks1986}}</ref>
}}

==Further reading==
* {{cite book |author-first=Jonathan |author-last=Bartlett |title=Programming from the Ground Up - An introduction to programming using linux assembly language |publisher=[[Bartlett Publishing]] |date=2004 |isbn=0-9752838-4-7 |url=http://programminggroundup.blogspot.com/ |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324110645/http://programminggroundup.blogspot.com/ |archive-date=2020-03-24}} [https://web.archive.org/web/20090206015549/http://download.savannah.gnu.org/releases-noredirect/pgubook/ProgrammingGroundUp-1-0-booksize.pdf]
* {{cite book |author-first=Robert |author-last=Britton |title=MIPS Assembly Language Programming |publisher=[[Prentice Hall]] |date=2003 |isbn=0-13-142044-5}}
* {{cite book |title=Assemblers, Compilers, and Program Translation |author-first=Peter |author-last=Calingaert |editor-first=Ellis |editor-last=Horowitz |editor-link=Ellis Horowitz |date=1979 |orig-year=1978-11-05 |series=Computer software engineering series |publisher=[[Computer Science Press, Inc.]] |publication-place=Potomac, Maryland, US |location=[[University of North Carolina at Chapel Hill]] |edition=1st printing, 1st |isbn=0-914894-23-4 |issn=0888-2088 |lccn=78-21905 |url=https://archive.org/details/assemblerscompil00cali |url-access=registration |access-date=2020-03-20 }} (2+xiv+270+6 pages)
* {{cite book |author-first=Jeff |author-last=Duntemann |title=Assembly Language Step-by-Step |publisher=[[Wiley (publisher)|Wiley]] |date=2000 |isbn=0-471-37523-3}}
* {{cite book |author-first=Randall |author-last=Hyde |title=The Art of Assembly Language |publisher=No Starch Press |edition=2nd |date=2010 |isbn=978-1593272074}}
* {{cite web |author-first=Ed |author-last=Jorgensen |title=x86-64 Assembly Language Programming with Ubuntu |url=http://www.egr.unlv.edu/~ed/assembly64.pdf}}
* {{cite web |author-first=Charles W. |author-last=Kann |title=Introduction to MIPS Assembly Language Programming |date=2015 |url=http://cupola.gettysburg.edu/cgi/viewcontent.cgi?article=1001&context=oer |access-date=2020-03-24 |url-status=live |archive-url=https://web.archive.org/web/20200324110918/https://cupola.gettysburg.edu/cgi/viewcontent.cgi?referer=&httpsredir=1&article=1001&context=oer |archive-date=2020-03-24}}
* {{cite journal |author-last=Kann |author-first=Charles W. |date=2021 |url=https://cupola.gettysburg.edu/oer/8/ |title=Introduction to Assembly Language Programming: From Soup to Nuts: ARM Edition|journal=Open Educational Resources }}
* {{cite book |author-first1=Peter |author-last1=Norton |author-link1=Peter Norton |author-first2=John |author-last2=Socha |author-link2=John Socha |title=Peter Norton's Assembly Language Book for the IBM PC |publisher=Brady Books |location=New York, US |date=1986}}
* {{cite book |author-first=Michael |author-last=Singer |title=PDP-11. Assembler Language Programming and Machine Organization |publisher=[[John Wiley & Sons]] |location=New York, US |date=1980}}
* {{cite book |author-first=Dominic |author-last=Sweetman |title=See MIPS Run |publisher=[[Morgan Kaufmann Publishers]] |date=1999 |isbn=1-55860-410-3}}
* {{cite book |author-first=John |author-last=Waldron |title=Introduction to RISC Assembly Language Programming |publisher=[[Addison Wesley]] |date=1998 |isbn=0-201-39828-1}}
* {{cite web |title=ASM Community Book |year=2009 |url=http://www.asmcommunity.net/book/ |access-date=2013-05-30 |url-status=dead |archive-url=https://web.archive.org/web/20130530074022/http://www.asmcommunity.net/book/ |archive-date=2013-05-30}} ("An online book full of helpful ASM info, tutorials and code examples" by the ASM Community, archived at the internet archive.)

==External links==
{{Sister project links|commons=Category:Assembly languages|wikt=assembly language|v=assembly language|b=Subject:Assembly languages|q=no|s=no}}
* [http://wiki.c2.com/?AssemblyLanguage Assembly Language] and [http://wiki.c2.com/?LearningAssemblyLanguage Learning Assembly Language] pages on [[WikiWikiWeb]]
* [http://www.azillionmonkeys.com/qed/asmexample.html Assembly Language Programming Examples]

{{Types of programming languages}}
{{Embedded systems}}
{{Authority control}}
{{Portal bar|Computer programming}}

{{DEFAULTSORT:Assembly Language}}
[[Category:Assembly languages|*Assembly language]]
[[Category:Computer-related introductions in 1949]]
[[Category:Embedded systems]]
[[Category:Low-level programming languages]]
[[Category:Programming language implementation]]
[[Category:Programming languages created in 1949]]