Assembly directives and pseudo-ops, Computer Engineering

Assembly directives and pseudo-ops:

Assembly directives are which instructions that executed by the assembler at assembly time, not by the CPU at run time. They can build the assembly of the program dependent on parameters input by the programmer, so that 1 program can be assembled with different ways, may be for different type of applications. They also can be used to direct presentation of the program to make it simple for the programmer to read and maintain it.

(For instance, pseudo-ops would be used to reserve storage areas and optionally their primary contents.) The names of pseudo-ops frequently start with a dot to differentiate them from machine instructions. Some assemblers also take favor of pseudo-instructions, which produce two or more machine instructions. Symbolic assemblers permit programmers to connect arbitrary names (labels or symbols) with memory locations. Generally, every variable and constant is given a name so instructions can reference those locations by their name, therefore promoting self-documenting code.  In the executable code, the name of each subroutine is connected with its entry point, so any calls to a subroutine can use its name. In Inside the subroutines, GOTO destinations are given particular labels. Some assemblers support local symbols which are radically distinct from normal symbols (for example, the use of "10$" for a GOTO destination).

Most of the assemblers provide flexible symbol management, permit programmers to manage different type of namespaces, automatically calculate offsets within data structures, and assign labels that refer to literal values or the result of easy computations performed by the assembler. The labels can also be used to initialize variables and constants with re -locatable addresses.

Assembly languages, like most of the other computer languages, give permission to comments to be added to assembly source code that is avoided by the assembler. Good use of comments is even more significant with assembly code than with higher-level languages like c, c ++, etc., as the meaning and purpose of a sequence of instructions is difficult to decipher from the code itself.

Intelligent use of these facilities can simplify the problems of coding and maintaining low-level code. Raw assembly source code as produced by compilers or disassembles-code without any comments, data definitions, or meaningful symbols-is quite hard to read when changes must be made.

Posted Date: 10/13/2012 3:10:06 AM | Location : United States







Related Discussions:- Assembly directives and pseudo-ops, Assignment Help, Ask Question on Assembly directives and pseudo-ops, Get Answer, Expert's Help, Assembly directives and pseudo-ops Discussions

Write discussion on Assembly directives and pseudo-ops
Your posts are moderated
Related Questions
Give the solutions for critical section problem? A solution to the critical section problem must specify the subsequent requirements. (a) Mutual exclusion (b) Progress (c)

data dictionary for online banking system in software engineering

Describe the types of flip-flops and latches. Flip-flops are of two types as illustrated below: a. Positive edge triggered b.  negative edge triggered Latches are

Presumably for heightened tension - first-order logic: As an aside, it's worth pointing out that - presumably for heightened tension - in most Sherlock Holmes books, the m

What is the difference between field-group header and other field groups? The header field group is a particular field group for the sort criteria.  The system automatically p

Eight-stage process - Conjunctive normal forms: Hence we notice the following eight-stage process converts any sentence with CNF as:  1.  Eliminate all arrow connectives by

Allocation of Bits among Opcode and Operand The trade-off here is between numbers of bits of opcode vs. the addressing capabilities. An interesting development in this regard i

voltage,current and power relation in a delta connection

Final Implementation of Object oriented modelling Final Implementation: At this phase, the final execution of classes and  relationships developed while object design takes

In a DTMF phone, digits are represented by: (A)  Orthogonal frequencies. (B)  Orthogonal Phases. (C)  Orthogonal codes. (D)  Orthogonal pulses. Ans: Di