Assembly Language
Assembly Language
Assembly language notation is another type of notation to represent machine instructions and
programs. A generic instruction to transfer content of a memory location LOC to processor
register R1 can be specified by the statement
Load R1, LOC
The contents of LOC are unchanged by the execution of the instruction, but the old contents of
register R1 are overwritten. The name Load is appropriate for the instruction because the
contents read from a memory location are loaded into a processor register.
Example 2. Adding of two numbers contained in processor register R1 and R2 and placing their
sum in R3 can be specified by the assembly-language statement
Add R3, R2, R1
In this case, register R1 and R2 hold the source operands, while R3 is the destination.
The English words Load and Add are used to denote the required operations. In the assembly-
language instructions of actual (commercial) processors, such operations are defined by using
mnemonics, which are typically abbreviations of the words describing the operations. For
example, the operation Load may be written as LD, while the operation Store, which transfers a
word from a processor register to the memory, may be written as STR or ST. Assembly
languages for different processors often use different mnemonics for a given operation.
x: memory address
When the processor gets the numeric data from memory to register, it again reverses the bytes.
There are two kinds of memory addresses −
Absolute address - a direct reference of specific location.
Segment address (or offset) - starting address of a memory segment with the offset value.
Data Registers
Four 32-bit data registers are used for arithmetic, logical, and other operations. These 32-bit
registers can be used in three ways −
As complete 32-bit data registers: EAX, EBX, ECX, EDX.
Lower halves of the 32-bit registers can be used as four 16-bit data registers: AX, BX,
CX and DX.
Lower and higher halves of the above-mentioned four 16-bit registers can be used as
eight 8-bit data registers: AH, AL, BH, BL, CH, CL, DH, and DL.
Some of these data registers have specific use in arithmetical operations.
AX is the primary accumulator; it is used in input/output and most arithmetic instructions. For
example, in multiplication operation, one operand is stored in EAX or AX or AL register
according to the size of the operand.
BX is known as the base register, as it could be used in indexed addressing.
CX is known as the count register, as the ECX, CX registers store the loop count in iterative
operations.
DX is known as the data register. It is also used in input/output operations. It is also used with
AX register along with DX for multiply and divide operations involving large values.
Pointer Registers
The pointer registers are 32-bit EIP, ESP, and EBP registers and corresponding 16-bit right
portions IP, SP, and BP. There are three categories of pointer registers −
Instruction Pointer (IP) − The 16-bit IP register stores the offset address of the next
instruction to be executed. IP in association with the CS register (as CS:IP) gives the
complete address of the current instruction in the code segment.
Stack Pointer (SP) − The 16-bit SP register provides the offset value within the program
stack. SP in association with the SS register (SS:SP) refers to be current position of data
or address within the program stack.
Base Pointer (BP) − The 16-bit BP register mainly helps in referencing the parameter
variables passed to a subroutine. The address in SS register is combined with the offset in
BP to get the location of the parameter. BP can also be combined with DI and SI as base
register for special addressing.
Index Registers
The 32-bit index registers, ESI and EDI, and their 16-bit rightmost portions. SI and DI, are used
for indexed addressing and sometimes used in addition and subtraction. There are two sets of
index pointers −
Source Index (SI) − It is used as source index for string operations.
Destination Index (DI) − It is used as destination index for string operations.
Control Registers
The 32-bit instruction pointer register and the 32-bit flags register combined are considered as
the control registers.
Many instructions involve comparisons and mathematical calculations and change the status of
the flags and some other conditional instructions test the value of these status flags to take the
control flow to other location.
The common flag bits are:
The common flag bits are:
Overflow Flag (OF) − It indicates the overflow of a high-order bit (leftmost bit) of data
after a signed arithmetic operation.
Direction Flag (DF) − It determines left or right direction for moving or comparing
string data. When the DF value is 0, the string operation takes left-to-right direction and
when the value is set to 1, the string operation takes right-to-left direction.
Interrupt Flag (IF) − It determines whether the external interrupts like keyboard entry,
etc., are to be ignored or processed. It disables the external interrupt when the value is 0
and enables interrupts when set to 1.
Trap Flag (TF) − It allows setting the operation of the processor in single-step mode.
The DEBUG program we used sets the trap flag, so we could step through the execution
one instruction at a time.
Sign Flag (SF) − It shows the sign of the result of an arithmetic operation. This flag is set
according to the sign of a data item following the arithmetic operation. The sign is
indicated by the high-order of leftmost bit. A positive result clears the value of SF to 0
and negative result sets it to 1.
Zero Flag (ZF) − It indicates the result of an arithmetic or comparison operation. A
nonzero result clears the zero flag to 0, and a zero result sets it to 1.
Auxiliary Carry Flag (AF) − It contains the carry from bit 3 to bit 4 following an
arithmetic operation; used for specialized arithmetic. The AF is set when a 1-byte
arithmetic operation causes a carry from bit 3 into bit 4.
Parity Flag (PF) − It indicates the total number of 1-bits in the result obtained from an
arithmetic operation. An even number of 1-bits clears the parity flag to 0 and an odd
number of 1-bits sets the parity flag to 1.
Carry Flag (CF) − It contains the carry of 0 or 1 from a high-order bit (leftmost) after an
arithmetic operation. It also stores the contents of last bit of a shift or rotate operation.
The following table indicates the position of flag bits in the 16-bit Flags register:
Flag: O D I T S Z A P C
Bit no: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Segment Registers
Segments are specific areas defined in a program for containing data, code and stack. There are
three main segments −
Code Segment − It contains all the instructions to be executed. A 16-bit Code Segment
register or CS register stores the starting address of the code segment.
Data Segment − It contains data, constants and work areas. A 16-bit Data Segment
register or DS register stores the starting address of the data segment.
Stack Segment − It contains data and return addresses of procedures or subroutines. It is
implemented as a 'stack' data structure. The Stack Segment register or SS register stores
the starting address of the stack.
Apart from the DS, CS and SS registers, there are other extra segment registers - ES (extra
segment), FS and GS, which provide additional segments for storing data.
In assembly programming, a program needs to access the memory locations. All memory
locations within a segment are relative to the starting address of the segment. A segment begins
in an address evenly divisible by 16 or hexadecimal 10. So, the rightmost hex digit in all such
memory addresses is 0, which is not generally stored in the segment registers.
The segment registers stores the starting addresses of a segment. To get the exact location of data
or instruction within a segment, an offset value (or displacement) is required. To reference any
memory location in a segment, the processor combines the segment address in the segment
register with the offset value of the location.
Assembly - System Calls
System calls are APIs for the interface between the user space and the kernel space. We have
already used the system calls. sys_write and sys_exit, for writing into the screen and exiting from
the program, respectively.
Linux System Calls
You can make use of Linux system calls in your assembly programs. You need to take the
following steps for using Linux system calls in your program −
Put the system call number in the EAX register.
Store the arguments to the system call in the registers EBX, ECX, etc.
Call the relevant interrupt (80h).
The result is usually returned in the EAX register.
There are six registers that store the arguments of the system call used. These are the EBX, ECX,
EDX, ESI, EDI, and EBP. These registers take the consecutive arguments, starting with the EBX
register. If there are more than six arguments, then the memory location of the first argument is
stored in the EBX register.
The following code snippet shows the use of the system call sys_exit −
mov eax,1 ; system call number (sys_exit)
int 0x80 ; call kernel
The following code snippet shows the use of the system call sys_write −
mov edx,4 ; message length
mov ecx,msg ; message to write
mov ebx,1 ; file descriptor (stdout)
mov eax,4 ; system call number (sys_write)
int 0x80 ; call kernel
All the syscalls are listed in /usr/include/asm/unistd.h, together with their numbers (the value to
put in EAX before you call int 80h).
The following table shows some of the system calls used in this tutorial −
1 sys_exit int - - - -
BYTE 1
WORD 2
DWORD 4
QWORD 8
TBYTE 10
Directive Purpose
Multiple Definitions
You can have multiple data definition statements in a program. For example −
choice DB 'Y' ;ASCII of y = 79H
number1 DW 12345 ;12345D = 3039H
number2 DD 12345679 ;123456789D = 75BCD15H
The assembler allocates contiguous memory for multiple variable definitions.
Multiple Initializations
The TIMES directive allows multiple initializations to the same value. For example, an array
named marks of size 9 can be defined and initialized to zero using the following statement −
marks TIMES 9 DW 0
The TIMES directive is useful in defining arrays and tables.
Assembly - Constants
There are several directives provided by NASM that define constants. We have already used the
EQU directive in previous chapters. We will particularly discuss three directives −
EQU
%assign
%define
The EQU Directive
The EQU directive is used for defining constants. The syntax of the EQU directive is as follows
−
CONSTANT_NAME EQU expression
For example,
TOTAL_STUDENTS equ 50
You can then use this constant value in your code, like −
mov ecx, TOTAL_STUDENTS
cmp eax, TOTAL_STUDENTS
The operand of an EQU statement can be an expression −
LENGTH equ 20
WIDTH equ 10
AREA equ length * width
Above code segment would define AREA as 200.
The %assign Directive
The %assign directive can be used to define numeric constants like the EQU directive. This
directive allows redefinition. For example, you may define the constant TOTAL as −
%assign TOTAL 10
Later in the code, you can redefine it as −
%assign TOTAL 20
This directive is case-sensitive.
The %define Directive
The %define directive allows defining both numeric and string constants. This directive is
similar to the #define in C. For example, you may define the constant PTR as −
%define PTR [EBP+4]
The above code replaces PTR by [EBP+4].
This directive also allows redefinition and it is case-sensitive.
Assembly - Arithmetic Instructions
The INC Instruction
The INC instruction is used for incrementing an operand by one. It works on a single operand
that can be either in a register or in memory.
Syntax
The INC instruction has the following syntax −
INC destination
The operand destination could be an 8-bit, 16-bit or 32-bit operand.
Example
INC EBX ; Increments 32-bit register
INC DL ; Increments 8-bit register
INC [count] ; Increments the count variable
The DEC Instruction
The DEC instruction is used for decrementing an operand by one. It works on a single operand
that can be either in a register or in memory.
Syntax
The DEC instruction has the following syntax −
DEC destination
The operand destination could be an 8-bit, 16-bit or 32-bit operand.
Example
segment .data
count dw 0
value db 15
segment .text
inc [count]
dec [value]
Sr.No. Scenarios
Example
MOV AL, 10
MOV DL, 25
MUL DL
...
MOV DL, 0FFH ; DL= -1
MOV AL, 0BEH ; AL = -66
IMUL DL
The DIV/IDIV Instructions
The division operation generates two elements - a quotient and a remainder. In case of
multiplication, overflow does not occur because double-length registers are used to keep the
product. However, in case of division, overflow may occur. The processor generates an interrupt
if overflow occurs.
The DIV (Divide) instruction is used for unsigned data and the IDIV (Integer Divide) is used for
signed data.
Syntax
The format for the DIV/IDIV instruction −
DIV/IDIV divisor
The dividend is in an accumulator. Both the instructions can work with 8-bit, 16-bit or 32-bit
operands. The operation affects all six status flags. Following section explains three cases of
division with different operand size −
Sr.No. Scenarios
2 OR OR operand1, operand2
Unconditional jump
This is performed by the JMP instruction. Conditional execution often involves a transfer of
1 control to the address of an instruction that does not follow the currently executing instruction.
Transfer of control may be forward, to execute a new set of instructions or backward, to re-
execute the same steps.
Conditional jump
2 This is performed by a set of jump instructions j<condition> depending upon the condition.
The conditional instructions transfer the control by breaking the sequential flow and they do it
by changing the offset value in IP.
Let us discuss the CMP instruction before discussing the conditional instructions.
CMP Instruction
The CMP instruction compares two operands. It is generally used in conditional execution. This
instruction basically subtracts one operand from the other for comparing whether the operands
are equal or not. It does not disturb the destination or source operands. It is used along with the
conditional jump instruction for decision making.
Syntax
CMP destination, source
CMP compares two numeric data fields. The destination operand could be either in register or in
memory. The source operand could be a constant (immediate) data, register or memory.
Example
CMP DX, 00 ; Compare the DX value with zero
JE L7 ; If yes, then jump to label L7
.
.
L7: ...
CMP is often used for comparing whether a counter value has reached the number of times a
loop needs to be run. Consider the following typical condition −
INC EDX
CMP EDX, 10 ; Compares whether the counter has reached 10
JLE LP1 ; If it is less than or equal to 10, then jump to LP1
Unconditional Jump
As mentioned earlier, this is performed by the JMP instruction. Conditional execution often
involves a transfer of control to the address of an instruction that does not follow the currently
executing instruction. Transfer of control may be forward, to execute a new set of instructions or
backward, to re-execute the same steps.
Syntax
The JMP instruction provides a label name where the flow of control is transferred immediately.
The syntax of the JMP instruction is −
JMP label
Example
The following code snippet illustrates the JMP instruction −
MOV AX, 00 ; Initializing AX to 0
MOV BX, 00 ; Initializing BX to 0
MOV CX, 01 ; Initializing CX to 1
L20:
ADD AX, 01 ; Increment AX
ADD BX, AX ; Add AX to BX
SHL CX, 1 ; shift left CX, this in turn doubles the CX value
JMP L20 ; repeats the statements
Conditional Jump
If some specified condition is satisfied in conditional jump, the control flow is transferred to a
target instruction. There are numerous conditional jump instructions depending upon the
condition and data.
Following are the conditional jump instructions used on signed data used for arithmetic
operations −
Following are the conditional jump instructions used on unsigned data used for logical
operations −
The following conditional jump instructions have special uses and check the value of flags −
JC Jump If Carry CF
JO Jump If Overflow OF
Double
Basic Instruction Operands at Byte Operation Word Operation word
Operation
Repetition Prefixes
The REP prefix, when set before a string instruction, for example - REP MOVSB, causes
repetition of the instruction based on a counter placed at the CX register. REP executes the
instruction, decreases CX by 1, and checks whether CX is zero. It repeats the instruction
processing until CX is zero.
The Direction Flag (DF) determines the direction of the operation.
Use CLD (Clear Direction Flag, DF = 0) to make the operation left to right.
Use STD (Set Direction Flag, DF = 1) to make the operation right to left.
The REP prefix also has the following variations:
REP: It is the unconditional repeat. It repeats the operation until CX is zero.
REPE or REPZ: It is conditional repeat. It repeats the operation while the zero flag
indicates equal/zero. It stops when the ZF indicates not equal/zero or when CX is zero.
REPNE or REPNZ: It is also conditional repeat. It repeats the operation while the zero
flag indicates not equal/zero. It stops when the ZF indicates equal/zero or when CX is
decremented to zero.
Assembly - Arrays
We have already discussed that the data definition directives to the assembler are used for
allocating storage for variables. The variable could also be initialized with some specific value.
The initialized value could be specified in hexadecimal, decimal or binary form.
For example, we can define a word variable 'months' in either of the following way −
MONTHS DW 12
MONTHS DW 0CH
MONTHS DW 0110B
The data definition directives can also be used for defining a one-dimensional array. Let us
define a one-dimensional array of numbers.
NUMBERS DW 34, 45, 56, 67, 75, 89
The above definition declares an array of six words each initialized with the numbers 34, 45, 56,
67, 75, 89. This allocates 2x6 = 12 bytes of consecutive memory space. The symbolic address of
the first number will be NUMBERS and that of the second number will be NUMBERS + 2 and
so on.
Let us take up another example. You can define an array named inventory of size 8, and initialize
all the values with zero, as −
INVENTORY DW 0
DW 0
DW 0
DW 0
DW 0
DW 0
DW 0
DW 0
Which can be abbreviated as −
INVENTORY DW 0, 0 , 0 , 0 , 0 , 0 , 0 , 0
The TIMES directive can also be used for multiple initializations to the same value. Using
TIMES, the INVENTORY array can be defined as:
INVENTORY TIMES 8 DW 0
Assembly - Procedures
Procedures or subroutines are very important in assembly language, as the assembly language
programs tend to be large in size. Procedures are identified by a name. Following this name, the
body of the procedure is described which performs a well-defined job. End of the procedure is
indicated by a return statement.
Syntax
Following is the syntax to define a procedure −
proc_name:
procedure body
...
ret
The procedure is called from another function by using the CALL instruction. The CALL
instruction should have the name of the called procedure as an argument as shown below −
CALL proc_name
The called procedure returns the control to the calling procedure by using the RET instruction.
Stacks Data Structure
A stack is an array-like data structure in the memory in which data can be stored and removed
from a location called the 'top' of the stack. The data that needs to be stored is 'pushed' into the
stack and data to be retrieved is 'popped' out from the stack. Stack is a LIFO data structure, i.e.,
the data stored first is retrieved last.
Assembly language provides two instructions for stack operations: PUSH and POP. These
instructions have syntaxes like −
PUSH operand
POP address/register
The memory space reserved in the stack segment is used for implementing stack. The registers
SS and ESP (or SP) are used for implementing the stack. The top of the stack, which points to the
last data item inserted into the stack is pointed to by the SS:ESP register, where the SS register
points to the beginning of the stack segment and the SP (or ESP) gives the offset into the stack
segment.
The stack implementation has the following characteristics −
Only words or doublewords could be saved into the stack, not a byte.
The stack grows in the reverse direction, i.e., toward the lower memory address
The top of the stack points to the last item inserted in the stack; it points to the lower byte
of the last word inserted.
As we discussed about storing the values of the registers in the stack before using them for some
use; it can be done in following way −
; Save the AX and BX registers in the stack
PUSH AX
PUSH BX
display:
mov ecx, 256
next:
push ecx
mov eax, 4
mov ebx, 1
mov ecx, achar
mov edx, 1
int 80h
pop ecx
mov dx, [achar]
cmp byte [achar], 0dh
inc byte [achar]
loop next
ret
section .data
achar db '0'
When the above code is compiled and executed, it produces the following result −
0123456789:;<=>?
@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}
...
...
Assembly - Recursion
A recursive procedure is one that calls itself. There are two kind of recursion: direct and indirect.
In direct recursion, the procedure calls itself and in indirect recursion, the first procedure calls a
second procedure, which in turn calls the first procedure.
Recursion could be observed in numerous mathematical algorithms. For example, consider the
case of calculating the factorial of a number. Factorial of a number is given by the equation −
Fact (n) = n * fact (n-1) for n > 0
For example: factorial of 5 is 1 x 2 x 3 x 4 x 5 = 5 x factorial of 4 and this can be a good example
of showing a recursive procedure. Every recursive algorithm must have an ending condition, i.e.,
the recursive calling of the program should be stopped when a condition is fulfilled. In the case
of factorial algorithm, the end condition is reached when n is 0.
Assembly - Macros
Writing a macro is another way of ensuring modular programming in assembly language.
A macro is a sequence of instructions, assigned by a name and could be used anywhere in
the program.
In NASM, macros are defined with %macro and %endmacro directives.
The macro begins with the %macro directive and ends with the %endmacro directive.
The Syntax for macro definition −
%macro macro_name number_of_params
<macro body>
%endmacro
Where, number_of_params specifies the number parameters, macro_name specifies the name of
the macro.
The macro is invoked by using the macro name along with the necessary parameters. When you
need to use some sequence of instructions many times in a program, you can put those
instructions in a macro and use it instead of writing the instructions all the time.
For example, a very common need for programs is to write a string of characters in the screen.
For displaying a string of characters, you need the following sequence of instructions −
mov edx,len ;message length
mov ecx,msg ;message to write
mov ebx,1 ;file descriptor (stdout)
mov eax,4 ;system call number (sys_write)
int 0x80 ;call kernel
In the above example of displaying a character string, the registers EAX, EBX, ECX and EDX
have been used by the INT 80H function call. So, each time you need to display on screen, you
need to save these registers on the stack, invoke INT 80H and then restore the original value of
the registers from the stack. So, it could be useful to write two macros for saving and restoring
data.
We have observed that, some instructions like IMUL, IDIV, INT, etc., need some of the
information to be stored in some particular registers and even return values in some specific
register(s). If the program was already using those registers for keeping important data, then the
existing data from these registers should be saved in the stack and restored after the instruction is
executed.
Assembly - File Management
The system considers any input or output data as stream of bytes. There are three standard file
streams −
Standard input (stdin),
Standard output (stdout), and
Standard error (stderr).
File Descriptor
A file descriptor is a 16-bit integer assigned to a file as a file id. When a new file is created or an
existing file is opened, the file descriptor is used for accessing the file.
File descriptor of the standard file streams - stdin, stdout and stderr are 0, 1 and 2, respectively.
File Pointer
A file pointer specifies the location for a subsequent read/write operation in the file in terms of
bytes. Each file is considered as a sequence of bytes. Each open file is associated with a file
pointer that specifies an offset in bytes, relative to the beginning of the file. When a file is
opened, the file pointer is set to zero.
File Handling System Calls
The following table briefly describes the system calls related to file handling −
The steps required for using the system calls are same, as we discussed earlier −
Put the system call number in the EAX register.
Store the arguments to the system call in the registers EBX, ECX, etc.
Call the relevant interrupt (80h).
The result is usually returned in the EAX register.
Creating and Opening a File
For creating and opening a file, perform the following tasks −
Put the system call sys_creat() number 8, in the EAX register.
Put the filename in the EBX register.
Put the file permissions in the ECX register.
The system call returns the file descriptor of the created file in the EAX register, in case of error,
the error code is in the EAX register.
Opening an Existing File
For opening an existing file, perform the following tasks −
Put the system call sys_open() number 5, in the EAX register.
Put the filename in the EBX register.
Put the file access mode in the ECX register.
Put the file permissions in the EDX register.
The system call returns the file descriptor of the created file in the EAX register, in case of error,
the error code is in the EAX register.
Among the file access modes, most commonly used are: read-only (0), write-only (1), and read-
write (2).
Reading from a File
For reading from a file, perform the following tasks −
Put the system call sys_read() number 3, in the EAX register.
Put the file descriptor in the EBX register.
Put the pointer to the input buffer in the ECX register.
Put the buffer size, i.e., the number of bytes to read, in the EDX register.
The system call returns the number of bytes read in the EAX register, in case of error, the error
code is in the EAX register.
Writing to a File
For writing to a file, perform the following tasks −
Put the system call sys_write() number 4, in the EAX register.
Put the file descriptor in the EBX register.
Put the pointer to the output buffer in the ECX register.
Put the buffer size, i.e., the number of bytes to write, in the EDX register.
The system call returns the actual number of bytes written in the EAX register, in case of error,
the error code is in the EAX register.
Closing a File
For closing a file, perform the following tasks −
Put the system call sys_close() number 6, in the EAX register.
Put the file descriptor in the EBX register.
The system call returns, in case of error, the error code in the EAX register.
Updating a File
For updating a file, perform the following tasks −
Put the system call sys_lseek () number 19, in the EAX register.
Put the file descriptor in the EBX register.
Put the offset value in the ECX register.
Put the reference position for the offset in the EDX register.
The reference position could be:
Beginning of file - value 0
Current position - value 1
End of file - value 2
The system call returns, in case of error, the error code in the EAX register.
Example
The following program creates and opens a file named myfile.txt, and writes a text 'Welcome to
Tutorials Point' in this file. Next, the program reads from the file and stores the data into a buffer
named info. Lastly, it displays the text as stored in info.
section .text
global _start ;must be declared for using gcc
section .data
file_name db 'myfile.txt'
msg db 'Welcome to Tutorials Point'
len equ $-msg
msg_done db 'Written to file', 0xa
len_done equ $-msg_done
section .bss
fd_out resb 1
fd_in resb 1
info resb 26
When the above code is compiled and executed, it produces the following result −
Written to file
Welcome to Tutorials Point
The sys_brk() system call is provided by the kernel, to allocate memory without the need of
moving it later. This call allocates memory right behind the application image in the memory.
This system function allows you to set the highest available address in the data section.
This system call takes one parameter, which is the highest memory address needed to be set. This
value is stored in the EBX register.
In case of any error, sys_brk() returns -1 or returns the negative error code itself. The following
example demonstrates dynamic memory allocation.
Assembly - Introduction
What is Assembly Language?
Each personal computer has a microprocessor that manages the computer's arithmetical, logical,
and control activities.
Each family of processors has its own set of instructions for handling various operations such as
getting input from keyboard, displaying information on screen and performing various other
jobs. These set of instructions are called 'machine language instructions'.
A processor understands only machine language instructions, which are strings of 1's and 0's.
However, machine language is too obscure and complex for using in software development. So,
the low-level assembly language is designed for a specific family of processors that represents
various instructions in symbolic code and a more understandable form.
Advantages of Assembly Language
Having an understanding of assembly language makes one aware of −
How programs interface with OS, processor, and BIOS;
How data is represented in memory and other external devices;
How the processor accesses and executes instruction;
How instructions access and process data;
How a program accesses external devices.
Other advantages of using assembly language are −
It requires less memory and execution time;
It allows hardware-specific complex jobs in an easier way;
It is suitable for time-critical jobs;
It is most suitable for writing interrupt service routines and other memory resident
programs.