A.1 Introduction A-7 text .align .globl main main: subu $sp,$sp,32 SW sra. 20($sp) sd $a0.32($sp) SW $0 24($sp) $0. 28($sp)】 100p: lw $t6.28($sp) mul $t7,$t6,$t6 1w $t8,24($sp) addu $t9.$t8,$t7 SW $t9.24($sp) addu $t0.$t6,1 SW $t0.28($sD) ble $t0.100.100p la sa0.str lw $a1.24($sp) jal printf move $v0,$0 lw $ra,20($sp】 addu $sp,$sp,32 sra data .align 0 str: .asciiz "The sum from 0..100 is &d\n" FIGURE A.1.4 The same routine written in assembly language with labels,but no com- ments.The commands that start with periods are assembler directives (see pages A-47-A-49)..text indicates that succeeding lines contain instructions..data indicates that they contain data..al i gn n indicates that the items on the succeeding lines should be aligned on a 2"byte boundary.Hence,.al ign 2 means the next item should be on a word boundary..globl ma in declares that ma i n is a global sym- bol that should be visible to code stored in other files.Finally,.asci iz stores a null-terminated string in memory. When to Use Assembly Language The primary reason to program in assembly language,as opposed to an available high-level language,is that the speed or size of a program is critically important. For example,consider a computer that controls a piece of machinery,such as a car's brakes.A computer that is incorporated in another device,such as a car,is called an embedded computer.This type of computer needs to respond rapidly and predictably to events in the outside world.Because a compiler introduces uncer-
A.1 Introduction A-7 When to Use Assembly Language The primary reason to program in assembly language, as opposed to an available high-level language, is that the speed or size of a program is critically important. For example, consider a computer that controls a piece of machinery, such as a car’s brakes. A computer that is incorporated in another device, such as a car, is called an embedded computer. This type of computer needs to respond rapidly and predictably to events in the outside world. Because a compiler introduces uncer- .text .align 2 .globl main main: subu $sp, $sp, 32 sw $ra, 20($sp) sd $a0, 32($sp) sw $0, 24($sp) sw $0, 28($sp) loop: lw $t6, 28($sp) mul $t7, $t6, $t6 lw $t8, 24($sp) addu $t9, $t8, $t7 sw $t9, 24($sp) addu $t0, $t6, 1 sw $t0, 28($sp) ble $t0, 100, loop la $a0, str lw $a1, 24($sp) jal printf move $v0, $0 lw $ra, 20($sp) addu $sp, $sp, 32 jr $ra .data .align 0 str: .asciiz "The sum from 0 .. 100 is %d\n" FIGURE A.1.4 The same routine written in assembly language with labels, but no comments. The commands that start with periods are assembler directives (see pages A-47–A-49). .text indicates that succeeding lines contain instructions. .data indicates that they contain data. .align n indicates that the items on the succeeding lines should be aligned on a 2n byte boundary. Hence, .align 2 means the next item should be on a word boundary. .globl main declares that main is a global symbol that should be visible to code stored in other files. Finally, .asciiz stores a null-terminated string in memory
A-8 Appendix A Assemblers,Linkers,and the SPIM Simulator #include <stdio.h> int main (int argc.char *argv[]) int i: int sum 0: for (i 0:i <100:ii 1)sum sum +ii: printf ("The sum from 0 .100 is %d\n",sum): FIGURE A.1.5 The routine written in the C programming language. High-level language program Program Compiler Linker Computer Assembly language program FIGURE A.1.6 Assembly language either is written by a programmer or is the output of a compiler. tainty about the time cost of operations,programmers may find it difficult to ensure that a high-level language program responds within a definite time inter- val-say,1 millisecond after a sensor detects that a tire is skidding.An assembly language programmer,on the other hand,has tight control over which instruc- tions execute.In addition,in embedded applications,reducing a program's size, so that it fits in fewer memory chips,reduces the cost of the embedded computer. A hybrid approach,in which most of a program is written in a high-level lan- guage and time-critical sections are written in assembly language,builds on the strengths of both languages.Programs typically spend most of their time execut- ing a small fraction of the program's source code.This observation is just the principle of locality that underlies caches(see Section 7.2 in Chapter 7). Program profiling measures where a program spends its time and can find the time-critical parts of a program.In many cases,this portion of the program can be made faster with better data structures or algorithms.Sometimes,however,sig- nificant performance improvements only come from recoding a critical portion of a program in assembly language
A-8 Appendix A Assemblers, Linkers, and the SPIM Simulator tainty about the time cost of operations, programmers may find it difficult to ensure that a high-level language program responds within a definite time interval—say, 1 millisecond after a sensor detects that a tire is skidding. An assembly language programmer, on the other hand, has tight control over which instructions execute. In addition, in embedded applications, reducing a program’s size, so that it fits in fewer memory chips, reduces the cost of the embedded computer. A hybrid approach, in which most of a program is written in a high-level language and time-critical sections are written in assembly language, builds on the strengths of both languages. Programs typically spend most of their time executing a small fraction of the program’s source code. This observation is just the principle of locality that underlies caches (see Section 7.2 in Chapter 7). Program profiling measures where a program spends its time and can find the time-critical parts of a program. In many cases, this portion of the program can be made faster with better data structures or algorithms. Sometimes, however, significant performance improvements only come from recoding a critical portion of a program in assembly language. #include <stdio.h> int main (int argc, char *argv[]) { int i; int sum = 0; for (i = 0; i <= 100; i = i + 1) sum = sum + i * i; printf ("The sum from 0 .. 100 is %d\n", sum); } FIGURE A.1.5 The routine written in the C programming language. FIGURE A.1.6 Assembly language either is written by a programmer or is the output of a compiler. Program Compiler Assembler Linker Computer High-level language program Assembly language program
A.1 Introduction A-9 This improvement is not necessarily an indication that the high-level language's compiler has failed.Compilers typically are better than programmers at producing uniformly high-quality machine code across an entire program.Pro- grammers,however,understand a program's algorithms and behavior at a deeper level than a compiler and can expend considerable effort and ingenuity improving small sections of the program.In particular,programmers often consider several procedures simultaneously while writing their code.Compilers typically compile each procedure in isolation and must follow strict conventions governing the use of registers at procedure boundaries.By retaining commonly used values in regis- ters,even across procedure boundaries,programmers can make a program run faster. Another major advantage of assembly language is the ability to exploit special- ized instructions,for example,string copy or pattern-matching instructions. Compilers,in most cases,cannot determine that a program loop can be replaced by a single instruction.However,the programmer who wrote the loop can replace it easily with a single instruction. Currently,a programmer's advantage over a compiler has become difficult to maintain as compilation techniques improve and machines'pipelines increase in complexity (Chapter 6). The final reason to use assembly language is that no high-level language is available on a particular computer.Many older or specialized computers do not have a compiler,so a programmer's only alternative is assembly language. Drawbacks of Assembly Language Assembly language has many disadvantages that strongly argue against its wide- spread use.Perhaps its major disadvantage is that programs written in assembly language are inherently machine-specific and must be totally rewritten to run on another computer architecture.The rapid evolution of computers discussed in Chapter 1 means that architectures become obsolete.An assembly language pro- gram remains tightly bound to its original architecture,even after the computer is eclipsed by new,faster,and more cost-effective machines. Another disadvantage is that assembly language programs are longer than the equivalent programs written in a high-level language.For example,the C program in Figure A.1.5 is 11 lines long,while the assembly program in Figure A.1.4 is 31 lines long.In more complex programs,the ratio of assembly to high-level lan- guage (its expansion factor)can be much larger than the factor of three in this example.Unfortunately,empirical studies have shown that programmers write roughly the same number of lines of code per day in assembly as in high-level lan- guages.This means that programmers are roughly x times more productive in a high-level language,where x is the assembly language expansion factor
A.1 Introduction A-9 This improvement is not necessarily an indication that the high-level language’s compiler has failed. Compilers typically are better than programmers at producing uniformly high-quality machine code across an entire program. Programmers, however, understand a program’s algorithms and behavior at a deeper level than a compiler and can expend considerable effort and ingenuity improving small sections of the program. In particular, programmers often consider several procedures simultaneously while writing their code. Compilers typically compile each procedure in isolation and must follow strict conventions governing the use of registers at procedure boundaries. By retaining commonly used values in registers, even across procedure boundaries, programmers can make a program run faster. Another major advantage of assembly language is the ability to exploit specialized instructions, for example, string copy or pattern-matching instructions. Compilers, in most cases, cannot determine that a program loop can be replaced by a single instruction. However, the programmer who wrote the loop can replace it easily with a single instruction. Currently, a programmer’s advantage over a compiler has become difficult to maintain as compilation techniques improve and machines’ pipelines increase in complexity (Chapter 6). The final reason to use assembly language is that no high-level language is available on a particular computer. Many older or specialized computers do not have a compiler, so a programmer’s only alternative is assembly language. Drawbacks of Assembly Language Assembly language has many disadvantages that strongly argue against its widespread use. Perhaps its major disadvantage is that programs written in assembly language are inherently machine-specific and must be totally rewritten to run on another computer architecture. The rapid evolution of computers discussed in Chapter 1 means that architectures become obsolete. An assembly language program remains tightly bound to its original architecture, even after the computer is eclipsed by new, faster, and more cost-effective machines. Another disadvantage is that assembly language programs are longer than the equivalent programs written in a high-level language. For example, the C program in Figure A.1.5 is 11 lines long, while the assembly program in Figure A.1.4 is 31 lines long. In more complex programs, the ratio of assembly to high-level language (its expansion factor) can be much larger than the factor of three in this example. Unfortunately, empirical studies have shown that programmers write roughly the same number of lines of code per day in assembly as in high-level languages. This means that programmers are roughly x times more productive in a high-level language, where x is the assembly language expansion factor
A-10 Appendix A Assemblers,Linkers,and the SPIM Simulator To compound the problem,longer programs are more difficult to read and understand and they contain more bugs.Assembly language exacerbates the prob- lem because of its complete lack of structure.Common programming idioms,such as if-then statements and loops,must be built from branches and jumps.The result- ing programs are hard to read because the reader must reconstruct every higher- level construct from its pieces and each instance of a statement may be slightly dif- ferent.For example,look at Figure A.1.4 and answer these questions:What type of loop is used?What are its lower and upper bounds? Elaboration:Compilers can produce machine language directly instead of relying on an assembler.These compilers typically execute much faster than those that invoke an assembler as part of compilation.However,a compiler that generates machine lan- guage must perform many tasks that an assembler normally handles,such as resolving addresses and encoding instructions as binary numbers.The trade-off is between com- pilation speed and compiler simplicity. Elaboration:Despite these considerations,some embedded applications are writ- ten in a high-level language.Many of these applications are large and complex pro- grams that must be extremely reliable.Assembly language programs are longer and more difficult to write and read than high-level language programs.This greatly increases the cost of writing an assembly language program and makes it extremely dif- ficult to verify the correctness of this type of program.In fact,these considerations led the Department of Defense,which pays for many complex embedded systems,to develop Ada,a new high-level language for writing embedded systems. A.2 Assemblers An assembler translates a file of assembly language statements into a file of binary external label Also called glo- machine instructions and binary data.The translation process has two major parts. bal label.A label referring to an The first step is to find memory locations with labels so the relationship between object that can be referenced symbolic names and addresses is known when instructions are translated.The sec- from files other than the one in ond step is to translate each assembly statement by combining the numeric equiva- which it is defined. lents of opcodes,register specifiers,and labels into a legal instruction.As shown in local label A label referring to Figure A.1.1,the assembler produces an output file,called an object file,which con- an object that can be used only tains the machine instructions,data,and bookkeeping information. within the file in which it is An object file typically cannot be executed because it references procedures or defined. data in other files.A label is external (also called global)if the labeled object can
A-10 Appendix A Assemblers, Linkers, and the SPIM Simulator To compound the problem, longer programs are more difficult to read and understand and they contain more bugs. Assembly language exacerbates the problem because of its complete lack of structure. Common programming idioms, such as if-then statements and loops, must be built from branches and jumps. The resulting programs are hard to read because the reader must reconstruct every higherlevel construct from its pieces and each instance of a statement may be slightly different. For example, look at Figure A.1.4 and answer these questions: What type of loop is used? What are its lower and upper bounds? Elaboration: Compilers can produce machine language directly instead of relying on an assembler. These compilers typically execute much faster than those that invoke an assembler as part of compilation. However, a compiler that generates machine language must perform many tasks that an assembler normally handles, such as resolving addresses and encoding instructions as binary numbers. The trade-off is between compilation speed and compiler simplicity. Elaboration: Despite these considerations, some embedded applications are written in a high-level language. Many of these applications are large and complex programs that must be extremely reliable. Assembly language programs are longer and more difficult to write and read than high-level language programs. This greatly increases the cost of writing an assembly language program and makes it extremely dif- ficult to verify the correctness of this type of program. In fact, these considerations led the Department of Defense, which pays for many complex embedded systems, to develop Ada, a new high-level language for writing embedded systems. An assembler translates a file of assembly language statements into a file of binary machine instructions and binary data. The translation process has two major parts. The first step is to find memory locations with labels so the relationship between symbolic names and addresses is known when instructions are translated. The second step is to translate each assembly statement by combining the numeric equivalents of opcodes, register specifiers, and labels into a legal instruction. As shown in Figure A.1.1, the assembler produces an output file, called an object file, which contains the machine instructions, data, and bookkeeping information. An object file typically cannot be executed because it references procedures or data in other files. A label is external (also called global) if the labeled object can A.2 Assemblers A.2 external label Also called global label. A label referring to an object that can be referenced from files other than the one in which it is defined. local label A label referring to an object that can be used only within the file in which it is defined
A.2 Assemblers A-11 be referenced from files other than the one in which it is defined.A label is local if the object can be used only within the file in which it is defined.In most assem- blers,labels are local by default and must be explicitly declared global.Subrou- tines and global variables require external labels since they are referenced from many files in a program.Local labels hide names that should not be visible to other modules-for example,static functions in C,which can only be called by other functions in the same file.In addition,compiler-generated names-for example,a name for the instruction at the beginning of a loop-are local so the compiler need not produce unique names in every file. Local and Global Labels Consider the program in Figure A.1.4 on page A-7.The subroutine has an external (global)label main.It also contains two local labels-1oop and EXAMPLE str-that are only visible with this assembly language file.Finally,the routine also contains an unresolved reference to an external label printf, which is the library routine that prints values.Which labels in Figure A.1.4 could be referenced from another file? Only global labels are visible outside of a file,so the only label that could be referenced from another file is main. ANSWER Since the assembler processes each file in a program individually and in isola- tion,it only knows the addresses of local labels.The assembler depends on another tool,the linker,to combine a collection of object files and libraries into an executable file by resolving external labels.The assembler assists the linker by pro- viding lists of labels and unresolved references. However,even local labels present an interesting challenge to an assembler. Unlike names in most high-level languages,assembly labels may be used before they are defined.In the example,in Figure A.1.4,the label str is used by the 1a instruction before it is defined.The possibility of a forward reference,like this forward reference A label that one,forces an assembler to translate a program in two steps:first find all labels is used before it is defined. and then produce instructions.In the example,when the assembler sees the 1a instruction,it does not know where the word labeled str is located or even whether str labels an instruction or datum
A.2 Assemblers A-11 be referenced from files other than the one in which it is defined. A label is local if the object can be used only within the file in which it is defined. In most assemblers, labels are local by default and must be explicitly declared global. Subroutines and global variables require external labels since they are referenced from many files in a program. Local labels hide names that should not be visible to other modules—for example, static functions in C, which can only be called by other functions in the same file. In addition, compiler-generated names—for example, a name for the instruction at the beginning of a loop—are local so the compiler need not produce unique names in every file. Since the assembler processes each file in a program individually and in isolation, it only knows the addresses of local labels. The assembler depends on another tool, the linker, to combine a collection of object files and libraries into an executable file by resolving external labels. The assembler assists the linker by providing lists of labels and unresolved references. However, even local labels present an interesting challenge to an assembler. Unlike names in most high-level languages, assembly labels may be used before they are defined. In the example, in Figure A.1.4, the label str is used by the la instruction before it is defined. The possibility of a forward reference, like this one, forces an assembler to translate a program in two steps: first find all labels and then produce instructions. In the example, when the assembler sees the la instruction, it does not know where the word labeled str is located or even whether str labels an instruction or datum. Local and Global Labels Consider the program in Figure A.1.4 on page A-7. The subroutine has an external (global) label main. It also contains two local labels—loop and str—that are only visible with this assembly language file. Finally, the routine also contains an unresolved reference to an external label printf, which is the library routine that prints values. Which labels in Figure A.1.4 could be referenced from another file? Only global labels are visible outside of a file, so the only label that could be referenced from another file is main. EXAMPLE ANSWER forward reference A label that is used before it is defined