Mod 1 - 18CS61 - Notes
Mod 1 - 18CS61 - Notes
L T P
SYSTEMSOF
TWAREAND
18CS61 Finite Automata
COMPILERS Core 3 2 - 50
Concepts
Module 1
Introduction to System Software, Machine Architecture of SIC and SIC/XE.
Assemblers: Basic assembler functions, machine dependent assembler features, machine independent
assembler features, assembler design options. Basic Loader Functions
Module 2
Introduction: Language Processors, The structure of a compiler, The evaluation of programming languages,
The science of building compiler, Applications of compiler technology, Programming language basics.
Lexical Analysis: The role of lexical analyzer, Input buffering, Specifications of token, recognition of tokens,
lexical analyzer generator, Finite automate.
Module 3
Syntax Analysis: Introduction, Role Of Parsers, Context Free Grammars, Writing a grammar, Top Down
VTUPulse.com
Parsers, Bottom-Up Parsers, Operator-Precedence Parsing.
Module 4
Lex and Yacc –The Simplest Lex Program, Grammars, Parser-Lexer Communication, A YACC Parser, The
Rules Section, Running LEX and YACC, LEX and Hand- Written Lexers, Using LEX - Regular Expression,
Examples of Regular Expressions, A Word Counting Program.
Using YACC – Grammars, Recursive Rules, Shift/Reduce Parsing, What YACC Cannot Parse, A YACC
Parser - The Definition Section, The Rules Section, The LEXER, Compiling and Running a Simple Parser,
Arithmetic Expressions and Ambiguity.
Module 5
Syntax Directed Translation, Intermediate code generation, Code generation.
MODULE - 1
1.0 Introduction
The subject introduces the design and implementation of system software. Software is set of
instructions or programs written to carry out certain task on digital computers. It is classified into
system software and application software. System software consists of a variety of programs that
support the operation of a computer. Application software focuses on an application or problem to be
solved. System software consists of a variety of programs that support the operation of a computer.
Examples for system software are Operating system, compiler, assembler, macro processor, loader or
linker, debugger, text editor, database management systems (some of them) and, software engineering
tools. These software’s make it possible for the user to focus on an application or other problem to be
solved, without needing to know the details of how the machine works internally.
VTUPulse.com
1.1 System Software and Machine Architecture
One characteristic in which most system software differs from application software is machine
dependency.
System software – support operation and use of computer application software and also
provides solution to a problem. Assembler translates mnemonic instructions into machine code. The
instruction formats, addressing modes etc., are of direct concern in assembler design. Similarly,
Compilers must generate machine language code, taking into account such hardware characteristics as
the number and type of registers and the machine instructions available. Operating systems are directly
concerned with the management of nearly all of the resources of a computing system.
There are aspects of system software that do not directly depend upon the type of computing
system, general design and logic of an assembler, general design and logic of a compiler and, code
optimization techniques, which are independent of target machines. Likewise, the process of linking
together independently assembled subprograms does not usually depend on the computer being used.
We discuss here the SIC machine architecture with respect to its Memory and Registers, Data
Formats, Instruction Formats, Addressing Modes, Instruction Set, Input and Output
Memory
There are 215 bytes in the computer memory that is 32,768 bytes, It uses Little Endian format
to store the numbers, 3 consecutive bytes form a word, and each location in memory contains 8-bit
bytes.
Registers
There are five registers, each 24 bits in length. Their mnemonic, number and use are given in
the following table.
VTUPulse.com
PC
SW
8
9
Program counter
Data Formats
Integers are stored as 24-bit binary numbers, 2’s complement representation is used for
negative values, characters are stored using their 8-bit ASCII codes, No floating-point hardware on the
standard version of SIC.
Instruction Formats
All machine instructions on the standard version of SIC have the 24-bit format as shown
above
ATMECE SS&C 18CS61
Addressing Modes
There are two addressing modes available, which are as shown in the above table. Parentheses
are used to indicate the contents of a register or a memory location.
Instruction Set
SIC provides, load and store instructions (LDA, LDX, STA, STX, etc.) . Integer arithmetic
operations: (ADD, SUB, MUL, DIV, etc.). All arithmetic operations involve registers A and a word in
memory, with the result being left in the register. Two instructions are provided for subroutine linkage.
COMP compares the value in register A with a word in memory; this instruction sets a condition code
CC to indicate the result. There are conditional jump instructions: (JLT, JEQ, JGT), these instructions
test the setting of CC and jump accordingly. JSUB jumps to the subroutine placing the return address
in register L, RSUB returns by jumping to the address contained in register L.
VTUPulse.com
Input and Output are performed by transferring 1 byte at a time to or from the rightmost 8 bits
of register A (accumulator). The Test Device (TD) instruction tests whether the addressed device is
ready to send or receive a byte of data . Read Data (RD), Write Data (WD) are used for reading or
writing the data.
LDA, STA, LDL, STL, LDX, STX ( A- Accumulator, L – Linkage Register, X – Index
Register), all uses 3-byte word. LDCH, STCH associated with characters uses 1-byte. There are no
memory-memory move instructions.
LDA FIVE
STA ALPHA
LDCH CHARZ
STCH C1
.
ALPHA RESW 1
FIVE WORD 5
CHARZ BYTE C’Z’
C1 RESB 1
LDA ALPHA
ADD INCR
SUB ONE
STA BEETA
……..
……..
……..
……..
ONE WORD 1
ALPHA RESW 1
VTUPulse.com
BEETA RESW 1
INCR RESW 1
Example 5 (To transfer two hundred bytes of data from input device to memory)
LDX ZERO
CLOOP TD INDEV
JEQ CLOOP
RD INDEV
STCH RECORD, X
TIX B200
JLT CLOOP
.
VTUPulse.com
.
INDEV BYTE X ‘F5’
RECORD RESB 200
ZERO WORD 0
B200 WORD 200
Example 6 (Subroutine to transfer two hundred bytes of data from input device to memory)
JSUB READ
………….
………….
READ LDX ZERO
CLOOP TD INDEV
JEQ CLOOP
RD INDEV
STCH RECORD, X
TIX B200 : add 1 to index compare 200 (B200)
JLT CLOOP
RSUB
……..
……..
INDEV BYTE X ‘F5’
RECORD RESB 200
ZERO WORD 0
B200 WORD 200
ATMECE SS&C 18CS61
Memory
Registers
Additional B, S, T, and F registers are provided by SIC/XE, in addition to the registers of SIC
B 3 Base register
S 4 General working register
T 5 General working register
F 6 Floating-point accumulator (48 bits)
Floating-point data type
Instruction Formats
The new set of instruction formats for SIC/XE machine architecture are as follows. Format 1
(1 byte): contains only operation code (straight from table). Format 2 (2 bytes): first eight bits for
operation code, next four for register 1 and following four for register 2. The numbers for the registers
go according to the numbers indicated at the registers section (ie, register T is replaced by hex 5, F is
replaced by hex 6). Format 3 (3 bytes): First 6 bits contain operation code, next 6 bits contain flags,
last 12 bits contain displacement for the address of the operand. Operation code uses only 6 bits, thus
the second hex digit will be affected by the values of the first two flags (n and i). The flags, in order,
are: n, i, x, b, p, and e. Its functionality is explained in the next section. The last flag e indicates the
instruction format (0 for 3 and 1 for 4). Format 4 (4 bytes): same as format 3 with an extra 2 hex digits
(8 bits) for addresses that require more than 12 bits to be represented.
ATMECE SS&C 18CS61
Format 1 (1 byte)
8
op
Format 2 (2 bytes)
8 4 4
op r1 r2
Format 3 (3 bytes)
6 1 1 1 1 1 1 12
op n i x b p e disp
VTUPulse.com
Format 4 (4 bytes)
op
1
n
1
i
1
x
1
b
1
p
1
e
20
address
Direct (x, b, and p all set to 0): operand address goes as it is. n and i are both set to the same
value, either 0 or 1. While in general that value is 1, if set to 0 for format 3 we can assume that the rest
of the flags (x, b, p, and e) are used
as a part of the address of the operand, to make the format compatible to the
SIC format
Relative (either b or p equal to 1 and the other one to 0): the address of the operand should be
added to the current value stored at the B register (if b = 1) or to the value stored at the PC register (if
p = 1)
Immediate (i = 1, n = 0): The operand value is already enclosed on the instruction (ie. lies on
the last 12/20 bits of the instruction)
ATMECE SS&C 18CS61
Indirect (i = 0, n = 1): The operand value points to an address that holds the address for the
operand value.
Indexed (x = 1): value to be added to the value stored at the register x to obtain real address of
the operand. This can be combined with any of the previous modes except immediate.
The various flag bits used in the above formats have the following meanings
Bits x, b, p: Used to calculate the target address using relative, direct, and indexed addressing Modes
b and p - both set to 0, disp field from format 3 instruction is taken to be the target address. For a
format 4 bits b and p are normally set to 0, 20 bit address is the target address
i=0, n=0 or i=1, n=1 Simple addressing, (TA):TA is taken as the address of the operand value
Two new relative addressing modes are available for use with instructions assembled using
VTUPulse.com
format 3.
TA=(B)+ disp
Base relative b=1,p=0
(0disp 4095)
Instruction Set
SIC/XE provides all of the instructions that are available on the standard version. In addition
we have, Instructions to load and store the new registers LDB, STB, etc, Floating-point arithmetic
operations, ADDF, SUBF, MULF, DIVF, Register move instruction : RMO, Register-to-register
arithmetic operations, ADDR, SUBR, MULR, DIVR and, Supervisor call instruction : SVC.
There are I/O channels that can be used to perform input and output while the CPU is
executing other instructions. Allows overlap of computing and I/O, resulting in more efficient system
operation. The instructions SIO, TIO, and HIO are used to start, test and halt the operation of I/O
channels.
ATMECE SS&C 18CS61
LDA #5
STA ALPHA
LDA #90
STCH C1
.
.
ALPHA RESW 1
C1 RESB 1
LDS INCR
LDA ALPHA
ADD S,A
SUB #1
STA BEETA
………….
…………..
ALPHA RESW 1
VTUPulse.com
BEETA RESW 1
INCR RESW 1
LDT #11
LDX #0 : X=0
MOVECH LDCH STR1, X : LOAD A FROM STR1
STCH STR2, X : STORE A TO STR2
TIXR T : ADD 1 TO X, TEST (T)
JLT MOVECH
……….
……….
………
STR1 BYTE C ‘HELLO WORLD’
STR2 RESB 11
Example 4 (To transfer two hundred bytes of data from input device to memory)
LDT #200
LDX #0
CLOOP TD INDEV
JEQ CLOOP
RD INDEV
ATMECE SS&C 18CS61
STCH RECORD, X
TIXR T
JLT CLOOP
.
.
INDEV BYTE X ‘F5’
RECORD RESB 200
Example 5 (Subroutine to transfer two hundred bytes of data from input device to memory)
JSUB READ
……….
……….
READ LDT #200
LDX #0
CLOOP TD INDEV
JEQ CLOOP
RD INDEV
STCH RECORD, X
TIXR T : add 1 to index compare T
JLT CLOOP
RSUB
……..
……..
INDEV BYTE X ‘F5’
VTUPulse.com
RECORD RESB 200
Assembler Design
Assembler is system software which is used to convert an assembly language program to its equivalent
object code. The input to the assembler is a source code written in assembly language (using
mnemonics) and the output is the object code. The design of an assembler depends upon the machine
architecture as the language used is mnemonic language.
So for the design of the assembler we need to concentrate on the machine architecture of the SIC/XE
machine. We need to identify the algorithms and the various data structures to be used. According to
the above required steps for assembling the assembler also has to handle assembler directives, these do
not generate the object code but directs the assembler to perform certain operation. These directives
are:
• SIC Assembler Directive:
– START: Specify name & starting address.
– END: End of the program, specify the first execution instruction.
– BYTE, WORD, RESB, RESW
– End of record: a null char(00)
VTUPulse.com
End of file: a zero length record
The assembler design can be done:
Single pass assembler
Multi-pass assembler
Single-pass Assembler:
In this case the whole process of scanning, parsing, and object code conversion is done in
single pass. The only problem with this method is resolving forward reference. This is shown with an
example below:
In the above example in line number 10 the instruction STL will store the linkage register with
the contents of RETADR. But during the processing of this instruction the value of this symbol is not
known as it is defined at the line number 95. Since I single-pass assembler the scanning, parsing and
object code conversion happens simultaneously. The instruction is fetched; it is scanned for tokens,
parsed for syntax and semantic validity. If it valid then it has to be converted to its equivalent object
code. For this the object code is generated for the opcode STL and the value for the symbol RETADR
need to be added, which is not available.
ATMECE SS&C 18CS61
Due to this reason usually the design is done in two passes. So a multi-pass assembler resolves
the forward references and then converts into the object code. Hence the process of the multi-pass
assembler can be as follows:
Pass-1
Assign addresses to all the statements
Save the addresses assigned to all labels to be used in Pass-2
Perform some processing of assembler directives such as RESW, RESB to find the length of
data areas for assigning the address values.
Defines the symbols in the symbol table(generate the symbol table)
Pass-2
Assemble the instructions (translating operation codes and looking up addresses).
Generate data values defined by BYTE, WORD etc.
Perform the processing of the assembler directives not done during pass-1.
Write the object program and assembler listing.
Assembler Design:
The most important things which need to be concentrated is the generation of Symbol table and
resolving forward references.
• Symbol Table:
– This is created during pass 1
– All the labels of the instructions are symbols
VTUPulse.com
– Table has entry for symbol name, address value.
• Forward reference:
– Symbols that are defined in the later part of the program are called forward
referencing.
– There will not be any address value for such symbols in the symbol table in pass 1.
Example Program:
The example program considered here has a main module, two subroutines
• Purpose of example program
- Reads records from input device (code F1)
- Copies them to output device (code 05)
- At the end of the file, writes EOF on the output device, then RSUB to the
operating system
• Data transfer (RD, WD)
-A buffer is used to store record
-Buffering is necessary for different I/O rates
-The end of each record is marked with a null character (00)16
-The end of the file is indicated by a zero-length record
Subroutines (JSUB, RSUB)
-RDREC, WRREC
-Save link register first before nested jump
ATMECE SS&C 18CS61
VTUPulse.com
ATMECE SS&C 18CS61
The first column shows the line number for that instruction, second column shows the addresses
allocated to each instruction. The third column indicates the labels given to the statement, and is
followed by the instruction consisting of opcode and operand. The last column gives the equivalent
VTUPulse.com
object code.
The object code later will be loaded into memory for execution. The simple object program we
use contains three types of records:
• Header record
- Col. 1 H
- Col. 2~7 Program name
- Col. 8~13 Starting address of object program (hex)
- Col. 14~19 Length of object program in bytes (hex)
• Text record
- Col. 1 T
- Col. 2~7 Starting address for object code in this record (hex)
- Col. 8~9 Length of object code in this record in bytes (hex)
- Col. 10~69 Object code, represented in hex (2 col. per byte)
• End record
- Col.1 E
- Col.2~7 Address of first executable instruction in object program (hex) “^” is only for
separation only
ATMECE SS&C 18CS61
All these steps except the second can be performed by sequential processing of the source program,
one line at a time. Consider the instruction
10 1000 LDA ALPHA 00-----
This instruction contains the forward reference, i.e. the symbol ALPHA is used is not yet
VTUPulse.com
defined. If the program is processed ( scanning and parsing and object code conversion) is done line-
by-line, we will be unable to resolve the address of this symbol. Due to this problem most of the
assemblers are designed to process the program in two passes.
In addition to the translation to object program, the assembler has to take care of handling
assembler directive. These directives do not have object conversion but gives direction to the
assembler to perform some function. Examples of directives are the statements like BYTE and
WORD, which directs the assembler to reserve memory locations without generating data values. The
other directives are START which indicates the beginning of the program and END indicating the end
of the program.
The assembled program will be loaded into memory for execution. The simple object program
contains three types of records: Header record, Text record and end record. The header record contains
the starting address and length. Text record contains the translated instructions and data of the
program, together with an indication of the addresses where these are to be loaded. The end record
marks the end of the object program and specifies the address where the execution is to begin.
Header record:
Col 1 H
Col. 2-7 Program name
Col 8-13 Starting address of object program (hexadecimal)
Col 14-19 Length of object program in bytes (hexadecimal)
ATMECE SS&C 18CS61
Text record:
Col. 1 T
Col 2-7. Starting address for object code in this record (hexadecimal)
Col 8-9 Length off object code in this record in bytes (hexadecimal)
Col 10-69 Object code, represented in hexadecimal (2 columns per byte of
object code)
End record:
Col. 1 E
Col 2-7 Address of first executable instruction in object program
(hexadecimal)
The assembler can be designed either as a single pass assembler or as a two pass assembler.
The general description of both passes is as given below:
VTUPulse.com
2. Algorithms and Data structure
The simple assembler uses two major internal data structures: the operation Code Table
(OPTAB) and the Symbol Table (SYMTAB).
OPTAB: It is used to lookup mnemonic operation codes and translates them to their machine
language equivalents. In more complex assemblers the table also contains information about
instruction format and length. In pass 1 the OPTAB is used to look up and validate the operation code
in the source program. In pass 2, it is used to translate the operation codes to machine language. In
simple SIC machine this process can be performed in either in pass 1 or in pass 2. But for machine like
SIC/XE that has instructions of different lengths, we must search OPTAB in the first pass to find the
instruction length for incrementing LOCCTR. In pass 2 we take the information from OPTAB to tell
us which instruction format to use in assembling the instruction, and any peculiarities of the object
code instruction.
OPTAB is usually organized as a hash table, with mnemonic operation code as the key. The
hash table organization is particularly appropriate, since it provides fast retrieval with a minimum of
searching. Most of the cases the OPTAB is a static table- that is, entries are not normally added to or
deleted from it. In such cases it is possible to design a special hashing function or other data structure
to give optimum performance for the particular set of keys being stored.
SYMTAB: This table includes the name and value for each label in the source program, together with
flags to indicate the error conditions (e.g., if a symbol is defined in two different places).
During Pass 1: labels are entered into the symbol table along with their assigned address value as they
ATMECE SS&C 18CS61
are encountered. All the symbols address value should get resolved at the pass 1.
During Pass 2: Symbols used as operands are looked up the symbol table to obtain the address value to
be inserted in the assembled instructions.
SYMTAB is usually organized as a hash table for efficiency of insertion and retrieval. Since entries
are rarely deleted, efficiency of deletion is the important criteria for optimization.
Both pass 1 and pass 2 require reading the source program. Apart from this an intermediate file is
created by pass 1 that contains each source statement together with its assigned address, error
indicators, etc. This file is one of the inputs to the pass 2. A copy of the source program is also an
input to the pass 2, which is used to retain the operations that may be performed during pass 1 (such as
scanning the operation field for symbols and addressing flags), so that these need not be performed
during pass 2. Similarly, pointers into OPTAB and SYMTAB is retained for each operation code and
symbol used. This avoids need to repeat many of the table-searching operations.
LOCCTR: Apart from the SYMTAB and OPTAB, this is another important variable which helps in
the assignment of the addresses. LOCCTR is initialized to the beginning address mentioned in the
START statement of the program. After each statement is processed, the length of the assembled
instruction is added to the LOCCTR to make it point to the next instruction. Whenever a label is
encountered in an instruction the LOCCTR value gives the address to be associated with that label.
VTUPulse.com
Begin
read first input line
if OPCODE = ‘START’ then begin
save #[Operand] as starting addr
initialize LOCCTR to starting address
write line to intermediate file
read next line
end( if START)
else
initialize LOCCTR to 0
While OPCODE != ‘END’ do
begin
if this is not a comment line then
begin
if there is a symbol in the LABEL field then
begin
search SYMTAB for LABEL
if found then
set error flag (duplicate symbol)
else
(if symbol)
search OPTAB for OPCODE
if found then
add 3 (instr length) to LOCCTR
else if OPCODE = ‘WORD’ then
add 3 to LOCCTR
ATMECE SS&C 18CS61
The algorithm scans the first statement START and saves the operand field (the address) as the
starting address of the program. Initializes the LOCCTR value to this address. This line is written to
the intermediate line. If no operand is mentioned the LOCCTR is initialized to zero. If a label is
encountered, the symbol has to be entered in the symbol table along with its associated address value.
If the symbol already exists that indicates an entry of the same symbol already exists. So an error flag
is set indicating a duplication of the symbol. It next checks for the mnemonic code, it searches for this
VTUPulse.com
code in the OPTAB. If found then the length of the instruction is added to the LOCCTR to make it
point to the next instruction. If the opcode is the directive WORD it adds a value 3 to the LOCCTR. If
it is RESW, it needs to add the number of data word to the LOCCTR. If it is BYTE it adds a value one
to the LOCCTR, if RESB it adds number of bytes. If it is END directive then it is the end of the
program it finds the length of the program by evaluating current LOCCTR – the starting address
mentioned in the operand field of the END directive. Each processed line is written to the intermediate
file.
Begin
read 1st input line
if OPCODE = ‘START’ then
begin
write listing line
read next input line
end
write Header record to object program
initialize 1st Text record
while OPCODE != ‘END’ do
begin
if this is not comment line then
begin
search OPTAB for OPCODE
if found then
begin
ATMECE SS&C 18CS61
end
add object code to Text record
end {if not comment}
write listing line
VTUPulse.com
read next input line
end
write listing line
read next input line
write last listing line
End {Pass 2}
Here the first input line is read from the intermediate file. If the opcode is START, then this line is
directly written to the list file. A header record is written in the object program which gives the
starting address and the length of the program (which is calculated during pass 1). Then the first text
record is initialized. Comment lines are ignored. In the instruction, for the opcode the OPTAB is
searched to find the object code. If a symbol is there in the operand field, the symbol table is searched
to get the address value for this which gets added to the object code of the opcode. If the address not
found then zero value is stored as operands address. An error flag is set indicating it as undefined. If
symbol itself is not found then store 0 as operand address and the object code instruction is assembled.
If the opcode is BYTE or WORD, then the constant value is converted to its equivalent object
code( for example, for character EOF, its equivalent hexadecimal value ‘454f46’ is stored). If the
object code cannot fit into the current text record, a new text record is created and the rest of the
instructions object code is listed. The text records are written to the object program. Once the whole
program is assemble and when the END directive is encountered, the End record is written.
Some of the features in the program depend on the architecture of the machine. If the program is for
SIC machine, then we have only limited instruction formats and hence limited addressing modes. We
have only single operand instructions. The operand is always a memory reference. Anything to be
fetched from memory requires more time. Hence the improved version of SIC/XE machine provides
more instruction formats and hence more addressing modes. The moment we change the machine
architecture the availability of number of instruction formats and the addressing modes changes.
Therefore the design usually requires considering two things: Machine-dependent features and
Machine-independent features.
3. Machine-Dependent Features:
The instruction formats depend on the memory organization and the size of the memory. In SIC
machine the memory is byte addressable. Word size is 3 bytes. So the size of the memory is 212 bytes.
Accordingly it supports only one instruction format. It has only two registers: register A and Index
register. Therefore the addressing modes supported by this architecture are direct, indirect, and
indexed. Whereas the memory of a SIC/XE machine is 220 bytes (1 MB). This supports four different
types of instruction types, they are:
1 byte instruction
2 byte instruction
VTUPulse.com
3 byte instruction
4 byte instruction
During pass 1 the registers can be entered as part of the symbol table itself. The value for these
registers is their equivalent numeric codes. During pass 2, these values are assembled along with the
mnemonics object code. If required a separate table can be created with the register names and their
equivalent numeric values.
In SIC/XE machine there are four instruction formats and five addressing modes. For formats and
ATMECE SS&C 18CS61
Among the instruction formats, format -3 and format-4 instructions are Register-Memory type of
instruction. One of the operand is always in a register and the other operand is in the memory. The
addressing mode tells us the way in which the operand from the memory is to be fetched.
There are two ways: Program-counter relative and Base-relative. This addressing mode can be
represented by either using format-3 type or format-4 type of instruction format. In format-3, the
instruction has the opcode followed by a 12-bit displacement value in the address field. Where as in
format-4 the instruction contains the mnemonic code followed by a 20-bit displacement value in the
address field.
2. Program-Counter Relative: In this usually format-3 instruction format is used. The instruction
contains the opcode followed by a 12-bit displacement value. The range of displacement values are
from 0 -2048. This displacement (should be small enough to fit in a 12-bit field) value is added to the
current contents of the program counter to get the target address of the operand required by the
instruction. This is relative way of calculating the address of the operand relative to the program
counter. Hence the displacement of the operand is relative to the current program counter value. The
following example shows how the address is calculated:
VTUPulse.com
3. Base-Relative Addressing Mode: in this mode the base register is used to mention the displacement
value. Therefore the target address is
TA = (base) + displacement value
This addressing mode is used when the range of displacement value is not sufficient. Hence the
operand is not relative to the instruction as in PC-relative addressing mode. Whenever this mode is
used it is indicated by using a directive BASE. The moment the assembler encounters this directive the
ATMECE SS&C 18CS61
next instruction uses base-relative addressing mode to calculate the target address of the operand.
When NOBASE directive is used then it indicates the base register is no more used to calculate the
target address of the operand. Assembler first chooses PC-relative, when the displacement field is not
enough it uses Base-relative.
For example:
In the above example the use of directive BASE indicates that Base-relative addressing mode is to
be used to calculate the target address. PC-relative is no longer used. The value of the LENGTH is
stored in the base register. If PC-relative is used then the target address calculated is:
VTUPulse.com
The LDB instruction loads the value of length in the base register which 0033. BASE directive
explicitly tells the assembler that it has the value of LENGTH.
If the symbol is referred in the instruction as the immediate operand then it is immediate with PC-
relative mode as shown in the example below:
VTUPulse.com
5. Indirect and PC-relative mode:
In this type of instruction the symbol used in the instruction is the address of the location which
contains the address of the operand. The address of this is found using PC-relative addressing mode.
For example:
The instruction jumps the control to the address location RETADR which in turn has the address of
the operand. If address of RETADR is 0030, the target address is then 0003 as calculated above.
to load these programs wherever there is place in the memory. Therefore the exact starting is not
known until the load time.
Absolute Program
In this the address is mentioned during assembling itself. This is called Absolute Assembly. Consider
the instruction:
This statement says that the register A is loaded with the value stored at location 102D. Suppose it
is decided to load and execute the program at location 2000 instead of location 1000. Then at address
102D the required value which needs to be loaded in the register A is no more available. The address
also gets changed relative to the displacement of the program. Hence we need to make some changes
in the address portion of the instruction so that we can load and execute the program at location 2000.
Apart from the instruction which will undergo a change in their operand address value as the program
load address changes. There exist some parts in the program which will remain same regardless of
where the program is being loaded.
Since assembler will not know actual location where the program will get loaded, it cannot make
the necessary changes in the addresses used in the program. However, the assembler identifies for the
loader those parts of the program which need modification. An object program that has the
information necessary to perform this kind of modification is called the relocatable program.
VTUPulse.com
The above diagram shows the concept of relocation. Initially the program is loaded at location
0000. The instruction JSUB is loaded at location 0006. The address field of this instruction contains
01036, which is the address of the instruction labeled RDREC. The second figure shows that if the
program is to be loaded at new location 5000. The address of the instruction JSUB gets modified to
new location 6036. Likewise the third figure shows that if the program is relocated at location 7420,
the JSUB instruction would need to be changed to 4B108456 that correspond to the new address of
RDREC.
The only part of the program that require modification at load time are those that specify
ATMECE SS&C 18CS61
direct addresses. The rest of the instructions need not be modified. The instructions which doesn’t
require modification are the ones that is not a memory address (immediate addressing) and PC-
relative, Base-relative instructions. From the object program, it is not possible to distinguish the
address and constant The assembler must keep some information to tell the loader. The object program
that contains the modification record is called a relocatable program.
For an address label, its address is assigned relative to the start of the program (START 0).
The assembler produces a Modification record to store the starting location and the length of the
address field to be modified. The command for the loader must also be a part of the object program.
The Modification has the following format:
Modification record
Col. 1 M
Col. 2-7 Starting location of the address field to be modified, relative to the
beginning of the program (Hex)
Col. 8-9 Length of the address field to be modified, in half-bytes (Hex)
One modification record is created for each address to be modified The length is stored in half-bytes
(4 bits) The starting location is the location of the byte containing the leftmost bits of the address field
to be modified. If the field contains an odd number of half-bytes, the starting location begins in the
middle of the first byte.
VTUPulse.com
In the above object code the red boxes indicate the addresses that need modifications. The object code
lines at the end are the descriptions of the modification records for those instructions which need
change if relocation occurs. M00000705 is the modification suggested for the statement at location
0007 and requires modification 5-half bytes. Similarly the remaining instructions indicate.
ATMECE SS&C 18CS61
3.2.1 Literals:
A literal is defined with a prefix = followed by a specification of the literal value.
Example:
The example above shows a 3-byte operand whose value is a character string EOF. The object
code for the instruction is also mentioned. It shows the relative displacement value of the location
where this value is stored. In the example the value is at location (002D) and hence the displacement
value is (010). As another example the given statement below shows a 1-byte literal with the
hexadecimal value ‘05’.
55
VTUPulse.com
It is important to understand the difference between a constant defined as a literal and a
constant defined as an immediate operand. In case of literals the assembler generates the specified
value as a constant at some other memory location In immediate mode the operand value is assembled
as part of the instruction itself. Example
All the literal operands used in a program are gathered together into one or more literal pools.
This is usually placed at the end of the program. The assembly listing of a program containing literals
usually includes a listing of this literal pool, which shows the assigned addresses and the generated
data values. In some cases it is placed at some other location in the object program. An assembler
directive LTORG is used. Whenever the LTORG is encountered, it creates a literal pool that contains
all the literal operands used since the beginning of the program. The literal pool definition is done
after LTORG is encountered. It is better to place the literals close to the instructions.
A literal table is created for the literals which are used in the program. The literal table
contains the literal name, operand value and length. The literal table is usually created as a hash table
on the literal name.
Implementation of Literals:
During Pass-1:
ATMECE SS&C 18CS61
The literal encountered is searched in the literal table. If the literal already exists, no action is
taken; if it is not present, the literal is added to the LITTAB and for the address value it waits till it
encounters LTORG for literal definition. When Pass 1 encounters a LTORG statement or the end of
the program, the assembler makes a scan of the literal table. At this time each literal currently in the
table is assigned an address. As addresses are assigned, the location counter is updated to reflect the
number of bytes occupied by each literal.
During Pass-2:
The assembler searches the LITTAB for each literal encountered in the instruction and
replaces it with its equivalent value as if these values are generated by BYTE or WORD. If a literal
represents an address in the program, the assembler must generate a modification relocation for, if it
all it gets affected due to relocation. The following figure shows the difference between the SYMTAB
and LITTAB
VTUPulse.com
3.2.2 Symbol-Defining Statements:
EQU Statement:
Most assemblers provide an assembler directive that allows the programmer to define symbols
and specify their values. The directive used for this EQU (Equate). The general form of the statement
is
Symbol EQU value
This statement defines the given symbol (i.e., entering in the SYMTAB) and assigning to it the value
specified. The value can be a constant or an expression involving constants and any other symbol
which is already defined. One common usage is to define symbolic names that can be used to improve
readability in place of numeric values. For example
+LDT #4096
This loads the register T with immediate value 4096, this does not clearly what exactly this value
indicates. If a statement is included as:
MAXLEN EQU 4096 and then
+LDT #MAXLEN
Then it clearly indicates that the value of MAXLEN is some maximum length value. When
ATMECE SS&C 18CS61
the assembler encounters EQU statement, it enters the symbol MAXLEN along with its value in the
symbol table. During LDT the assembler searches the SYMTAB for its entry and its equivalent value
as the operand in the instruction. The object code generated is the same for both the options discussed,
but is easier to understand. If the maximum length is changed from 4096 to 1024, it is difficult to
change if it is mentioned as an immediate value wherever required in the instructions. We have to scan
the whole program and make changes wherever 4096 is used. If we mention this value in the
instruction through the symbol defined by EQU, we may not have to search the whole program but
change only the value of MAXLENGTH in the EQU statement (only once).
Another common usage of EQU statement is for defining values for the general-purpose
registers. The assembler can use the mnemonics for register usage like a-register A , X – index register
and so on. But there are some instructions which requires numbers in place of names in the
instructions. For example in the instruction RMO 0,1 instead of RMO A,X. The programmer can
assign the numerical values to these registers using EQU directive.
A EQU 0
X EQU 1 and so on
These statements will cause the symbols A, X, L… to be entered into the symbol table with
their respective values. An instruction RMO A, X would then be allowed. As another usage if in a
machine that has many general purpose registers named as R1, R2,…, some may be used as base
register, some may be used as accumulator. Their usage may change from one program to another. In
this case we can define these requirement using EQU statements.
BASE EQU R1
INDEX EQU R2
VTUPulse.com
COUNT EQU R3
One restriction with the usage of EQU is whatever symbol occurs in the right hand side of the EQU
should be predefined. For example, the following statement is not valid:
As the symbol ALPHA is assigned to BETA before it is defined. The value of ALPHA is not known.
ORG Statement:
This directive can be used to indirectly assign values to the symbols. The directive is usually
called ORG (for origin). Its general format is:
ORG value
Where value is a constant or an expression involving constants and previously defined symbols. When
this statement is encountered during assembly of a program, the assembler resets its location counter
(LOCCTR) to the specified value. Since the values of symbols used as labels are taken from
LOCCTR, the ORG statement will affect the values of all labels defined until the next ORG is
encountered. ORG is used to control assignment storage in the object program. Sometimes altering the
values may result in incorrect assembly.
ORG can be useful in label definition. Suppose we need to define a symbol table with the
following structure:
SYMBOL 6 Bytes
VALUE 3 Bytes
ATMECE SS&C 18CS61
FLAG 2 Bytes
The symbol field contains a 6-byte user-defined symbol; VALUE is a one-word representation
VTUPulse.com
of the value assigned to the symbol; FLAG is a 2-byte field specifies symbol type and other
information. The space for the ttable can be reserved by the statement:
STAB RESB 1100
If we want to refer to the entries of the table using indexed addressing, place the offset value
of the desired entry from the beginning of the table in the index register. To refer to the fields
SYMBOL, VALUE, and FLAGS individually, we need to assign the values first as shown below:
To retrieve the VALUE field from the table indicated by register X, we can write a statement:
LDA VALUE, X
The same thing can also be done using ORG statement in the following way:
The first statement allocates 1100 bytes of memory assigned to label STAB. In the second
statement the ORG statement initializes the location counter to the value of STAB. Now the LOCCTR
points to STAB. The next three lines assign appropriate memory storage to each of SYMBOL,
VALUE and FLAG symbols. The last ORG statement reinitializes the LOCCTR to a new value after
skipping the required number of memory for the table STAB (i.e., STAB+1100).
While using ORG, the symbol occurring in the statement should be predefined as is required in EQU
statement. For example for the sequence of statements below:
ORG ALPHA
BYTE1 RESB 1
BYTE2 RESB 1
BYTE3 RESB 1
ORG
ALPHA RESB 1
The sequence could not be processed as the symbol used to assign the new location counter value is
not defined. In first pass, as the assembler would not know what value to assign to ALPHA, the other
symbol in the next lines also could not be defined in the symbol table. This is a kind of problem of the
forward reference.
3.2.3 Expressions:
VTUPulse.com
Assemblers also allow use of expressions in place of operands in the instruction. Each such
expression must be evaluated to generate a single operand value or address. Assemblers generally
arithmetic expressions formed according to the normal rules using arithmetic operators +, - *, /.
Division is usually defined to produce an integer result. Individual terms may be constants, user-
defined symbols, or special terms. The only special term used is * ( the current value of location
counter) which indicates the value of the next unassigned memory location. Thus the statement
BUFFEND EQU *
Assigns a value to BUFFEND, which is the address of the next byte following the buffer area. Some
values in the object program are relative to the beginning of the program and some are absolute
(independent of the program location, like constants). Hence, expressions are classified as either
absolute expression or relative expressions depending on the type of value they produce.
Absolute Expressions: The expression that uses only absolute terms is absolute expression. Absolute
expression may contain relative term provided the relative terms occur in pairs with opposite signs for
each pair. Example:
Relative Expressions: All the relative terms except one can be paired as described in “absolute”. The
ATMECE SS&C 18CS61
Handling the type of expressions: to find the type of expression, we must keep track the type of
symbols used. This can be achieved by defining the type in the symbol table against each of the
symbol as shown in the table below:
Program blocks allow the generated machine instructions and data to appear in the object
program in a different order by Separating blocks for storing code, data, stack, and larger data block.
Assembler Directive USE:
USE [blockname]
At the beginning, statements are assumed to be part of the unnamed (default) block. If no USE
statements are included, the entire program belongs to this single block. Each program block may
actually contain several separate segments of the source program. Assemblers rearrange these
VTUPulse.com
segments to gather together the pieces of each block and assign address. Separate the program into
blocks in a particular order. Large buffer area is moved to the end of the object program. Program
readability is better if data areas are placed in the source program close to the statements that
reference them.
Example Code
ATMECE SS&C 18CS61
VTUPulse.com
ATMECE SS&C 18CS61
VTUPulse.com
the label
Indicate the block length as the latest value of LOCCTR for each block at the end of Pass1
Assign to each block a starting address in the object program by concatenating the program
blocks in a particular order
Pass 2
Calculate the address for each symbol relative to the start of the object program by adding
The location of the symbol relative to the start of its block
The starting address of this block
A control section is a part of the program that maintains its identity after assembly; each
control section can be loaded and relocated independently of the others. Different control sections are
most often used for subroutines or other logical subdivisions. The programmer can assemble, load, and
manipulate each of these control sections separately.
Because of this, there should be some means for linking control sections together. For
example, instructions in one control section may refer to the data or instructions of other control
sections. Since control sections are independently loaded and relocated, the assembler is unable to
process these references in the usual way. Such references between different control sections are
called external references.
The assembler generates the information about each of the external references that will allow
the loader to perform the required linking. When a program is written using multiple control sections,
ATMECE SS&C 18CS61
Control sections differ from program blocks in that they are handled separately by the assembler.
Symbols that are defined in one control section may not be used directly another control section; they
must be identified as external reference for the loader to handle. The external references are indicated
by two assembler directives:
VTUPulse.com
ATMECE SS&C 18CS61
VTUPulse.com
Case 1
Case 2
There are two external references in the expression, BUFEND and BUFFER.
The assembler inserts a value of zero
passes information to the loader
Add to this data area the address of BUFEND
Subtract from this data area the address of BUFFER
Case 3
On line 107, BUFEND and BUFFER are defined in the same control section and the expression can be
calculated immediately.
VTUPulse.com
ATMECE SS&C 18CS61
VTUPulse.com
The assembler must also include information in the object program that will cause the loader to insert
the proper value where they are required. The assembler maintains two new record in the object code
and a changed version of modification record.
Modification record
Col. 1 M
Col. 2-7 Starting address of the field to be modified (hexadecimal)
Col. 8-9 Length of the field to be modified, in half-bytes (hexadecimal)
Col.11-16 External symbol whose value is to be added to or subtracted from
the indicated field
A define record gives information about the external symbols that are defined in this control section,
i.e., symbols named by EXTDEF.
A refer record lists the symbols that are used as external references by the control section, i.e., symbols
named by EXTREF.
The new items in the modification record specify the modification to be performed: adding or
subtracting the value of some external symbol. The symbol used for modification my be defined either
in this control section or in another section.
The object program is shown below. There is a separate object program for each of the control
sections. In the Define Record and refer record the symbols named in EXTDEF and EXTREF are
included.
In the case of Define, the record also indicates the relative address of each external symbol
within the control section.
VTUPulse.com
For EXTREF symbols, no address information is available. These symbols are simply named
in the Refer record.
ATMECE SS&C 18CS61
VTUPulse.com
Handling Expressions in Multiple Control Sections:
The existence of multiple control sections that can be relocated independently of one another
makes the handling of expressions complicated. It is required that in an expression that all the relative
terms be paired (for absolute expression), or that all except one be paired (for relative expressions).
When it comes in a program having multiple control sections then we have an extended
restriction that:
Both terms in each pair of an expression must be within the same control section
o If two terms represent relative locations within the same control section , their
difference is an absolute value (regardless of where the control section is located.
Legal: BUFEND-BUFFER (both are in the same control section)
o If the terms are located in different control sections, their difference has a value that is
unpredictable.
Illegal: RDREC-COPY (both are of different control section) it is the
difference in the load addresses of the two control sections. This value
depends on the way run-time storage is allocated; it is unlikely to be of any
use.
o The assembler evaluates all of the terms it can, combines these to form an initial
expression value, and generates Modification records.
o The loader checks the expression for errors and finishes the evaluation.
The main problem in designing the assembler using single pass was to resolve forward references. We
can avoid to some extent the forward references by:
Eliminating forward reference to data items, by defining all the storage reservation statements
at the beginning of the program rather at the end.
Unfortunately, forward reference to labels on the instructions cannot be avoided. (forward
jumping)
To provide some provision for handling forward references by prohibiting forward references
VTUPulse.com
to data items.
Load-and-Go Assembler
Load-and-go assembler generates their object code in memory for immediate execution.
No object program is written out, no loader is needed.
It is useful in a system with frequent program development and testing
o The efficiency of the assembly process is an important consideration.
Programs are re-assembled nearly every time they are run; efficiency of the assembly process
is an important consideration.
ATMECE SS&C 18CS61
VTUPulse.com
Forward Reference in One-Pass Assemblers: In load-and-Go assemblers when a forward reference
is encountered :
Omits the operand address if the symbol has not yet been defined
Enters this undefined symbol into SYMTAB and indicates that it is undefined
Adds the address of this operand address to a list of forward references associated with the
SYMTAB entry
When the definition for the symbol is encountered, scans the reference list and inserts the
address.
At the end of the program, reports the error if there are still SYMTAB entries indicated
undefined symbols.
For Load-and-Go assembler
o Search SYMTAB for the symbol named in the END statement and jumps to this
location to begin execution if there is no error
The status is that upto this point the symbol RREC is referred once at location 2013, ENDFIL at 201F
and WRREC at location 201C. None of these symbols are defined. The figure shows that how the
ATMECE SS&C 18CS61
pending definitions along with their addresses are included in the symbol table.
The status after scanning line 160, which has encountered the definition of RDREC and
VTUPulse.com
ENDFIL is as given below:
If the operand contains an undefined symbol, use 0 as the address and write the Text record to
the object program.
Forward references are entered into lists as in the load-and-go assembler.
When the definition of a symbol is encountered, the assembler generates another Text record
with the correct operand address of each entry in the reference list.
When loaded, the incorrect address 0 will be updated by the latter Text record containing the
symbol definition.
VTUPulse.com
Multi_Pass Assembler:
For a two pass assembler, forward references in symbol definition are not allowed:
ALPHA EQU BETA
BETA EQU DELTA
DELTA RESW 1
o Symbol definition must be completed in pass 1.
Prohibiting forward references in symbol definition is not a serious inconvenience.
o Forward references tend to create difficulty for a person reading the program.
VTUPulse.com
Multi-Pass Assembler (Figure 2.21 of Beck): Example for forward reference in Symbol Defining
Statements:
ATMECE SS&C 18CS61
VTUPulse.com