CMSC 313 Assembly Language and Computer Organization Topics

CMSC 313 Assembly Language and Computer Organization Topics: n n n Theme Programming in C Great realities of computer systems How this fits within CS curriculum Logistical issues

Course Theme n Abstraction is good, but don’t forget reality! Most CS courses emphasize abstraction n n Abstract data types Asymptotic analysis These abstractions have limits n n Especially in the presence of bugs Need to understand underlying implementations Useful outcomes n Become more effective programmers l Able to find and eliminate bugs efficiently l Able to tune program performance n Prepare for later “systems” classes in CS & ECE l Compilers, Operating Systems, Networks, Computer – 2– Architecture, Embedded Systems CMSC 313, F ‘ 10

Programming in C l We assume you have experience in Java or other high-level language (e. g. C++) that uses the same syntax l C is “closer” to the hardware than other languages n You are responsible for everything that happens l Array index validation n n You must understand how the computer works to write efficient, portable code Pointers, dynamic memory allocation must be handled by your code l Powerful, but dangerous l No garbage collector like Java l Functions are the focus, there are no objects n – 3– Encapsulation is difficult at best CMSC 313, F ‘ 10

Memory Referencing Errors C and C++ do not provide any memory protection n Out of bounds array references n Invalid pointer values Abuses of malloc/free n Can lead to nasty bugs n n Whether or not bug has any effect depends on system and compiler Action at a distance l Corrupted object logically unrelated to one being accessed l Effect of bug may be first observed long after it is generated How can I deal with this? n n – 4– n Program in Java or ML Understand what possible interactions may occur Use or develop tools to detect referencing errors CMSC 313, F ‘ 10

Great Reality #1 Ints are not Integers, Floats are not Reals Examples n Is x 2 ≥ 0? l Floats: Yes! l Ints: » 40000 * 40000 --> 160000 » 50000 * 50000 --> ? ? n Is (x + y) + z = x + (y + z)? l Unsigned & Signed Ints: Yes! l Floats: » (1 e 20 + -1 e 20) + 3. 14 --> 3. 14 » 1 e 20 + (-1 e 20 + 3. 14) --> ? ? – 5– CMSC 313, F ‘ 10

Computer Arithmetic Does not generate random values n Arithmetic operations have important mathematical properties Cannot assume “usual” properties n n Due to finiteness of representations Integer operations satisfy “ring” properties l Commutativity, associativity, distributivity n Floating point operations satisfy “ordering” properties l Monotonicity, values of signs Observation n n – 6– Need to understand which abstractions apply in which contexts Important issues for compiler writers and serious application programmers CMSC 313, F ‘ 10

Great Reality #2 You’ve got to know assembly Chances are, you’ll never write a program in assembly n Compilers are much better & more patient than you are Understanding assembly key to machine-level execution model n Behavior of programs in presence of bugs l High-level language model breaks down n Tuning program performance l Understanding sources of program inefficiency n Implementing system software l Compiler has machine code as target l Operating systems must manage process state n Creating / fighting malware l x 86 assembly is the language of choice! – 7– CMSC 313, F ‘ 10

Assembly Code Example Time Stamp Counter n Special 64 -bit register in Intel-compatible machines n Incremented every clock cycle Read with rdtsc instruction n Application n Measure time required by procedure l In units of clock cycles double t; start_counter(); P(); t = get_counter(); printf("P required %f clock cyclesn", t); – 8– CMSC 313, F ‘ 10

Code to Read Counter n Write small amount of assembly code using GCC’s asm facility n Inserts assembly code into machine code generated by compiler static unsigned cyc_hi = 0; static unsigned cyc_lo = 0; /* Set *hi and *lo to the high and low order bits of the cycle counter. */ void access_counter(unsigned *hi, unsigned *lo) { asm("rdtsc; movl %%edx, %0; movl %%eax, %1" : "=r" (*hi), "=r" (*lo) : : "%edx", "%eax"); } – 9– CMSC 313, F ‘ 10

Great Reality #3 Memory Matters: Random Access Memory is an un-physical abstraction Memory is not unbounded n n It must be allocated and managed Many applications are memory dominated Memory referencing bugs especially pernicious n Effects are distant in both time and space Memory performance is not uniform n n – 10 – Cache and virtual memory effects can greatly affect program performance Adapting program to characteristics of memory system can lead to major speed improvements CMSC 313, F ‘ 10

Memory Referencing Bug Example double fun(int i) { double d[1] = {3. 14}; long int a[2]; a[i] = 1073741824; /* Possibly out of bounds */ return d[0]; } fun(0) fun(1) fun(2) fun(3) fun(4) – 11 – –> –> –> 3. 14 3. 1399998664856 2. 00000061035156 3. 14, then segmentation fault CMSC 313, F ‘ 10

Referencing Bug Explanation n n – 12 – Saved State 4 d 7 … d 4 3 d 3 … d 0 2 a[1] 1 a[0] 0 Location accessed by fun(i) C does not implement bounds checking Out of range write can affect other parts of program state CMSC 313, F ‘ 10

Memory System Performance Example void copyij(int { int i, j; for (i = 0; i for (j = 0; dst[i][j] } src[2048], dst[2048]) < 2048; i++) j < 2048; j++) = src[i][j]; 59, 393, 288 clock cycles void copyji(int { int i, j; for (j = 0; j for (i = 0; dst[i][j] } n < 2048; j++) i < 2048; i++) = src[i][j]; 1, 277, 876 clock cycles 21. 5 times slower! n src[2048], dst[2048]) (Measured on 2 GHz Intel Pentium 4) Hierarchical memory organization Performance depends on access patterns l Including how step through multi-dimensional array – 13 – CMSC 313, F ‘ 10

The Memory Mountain Read throughput (MB/s) 1200 Pentium III Xeon 550 MHz 16 KB on-chip L 1 d-cache 16 KB on-chip L 1 i-cache 512 KB off-chip unified L 2 cache copyij 1000 L 1 800 copyji 600 400 xe L 2 200 – 14 – 2 k 8 k 32 k 128 k 512 k 2 m 8 m s 15 s 13 s 11 s 9 Stride (words) Mem s 7 s 5 s 3 s 1 0 Working set size (bytes) CMSC 313, F ‘ 10

Great Reality #4 Computers do more than execute programs They need to get data in and out n I/O system critical to program reliability and performance They communicate with each other over networks n Many system-level issues arise in presence of network l Concurrent operations by autonomous processes l Coping with unreliable media l Cross platform compatibility l Complex performance issues – 15 – CMSC 313, F ‘ 10

Role within Curriculum CMSC 421 Operating Systems CMSC 411 Architecture Exec. Model Memory System CMSC 431 Compilers Processes Machine Code Mem. Mgmt C Programming CMSC 313 Systems Foundation of Computer Systems n CMSC 201 Intro to Programming – 16 – Underlying principles for hardware, software CMSC 202 OOP in Java CMSC 313, F ‘ 10

Course Perspective Most Systems Courses are Builder-Centric n Computer Architecture l Design pipelined processor in Verilog n Operating Systems l Implement large portions of operating system n Compilers l Write compiler for simple language n Networking l Implement and simulate network protocols – 17 – CMSC 313, F ‘ 10

Course Perspective (Cont. ) Our Course is Programmer-Centric n Purpose is to show by knowing more about the underlying system, one can be more effective as a programmer n Enable you to l Write programs that are more reliable and efficient l Incorporate features that require hooks into OS » E. g. , concurrency, signal handlers n Not just a course for dedicated hackers l We bring out the hidden hacker in everyone n – 18 – Cover material in this course that you won’t see elsewhere CMSC 313, F ‘ 10

Textbooks Randal E. Bryant and David R. O’Hallaron, n n n “Computer Systems: A Programmer’s Perspective”, Prentice Hall 2003. http: //csapp. cs. cmu. edu This book really matters for the course! l How to solve labs l Practice problems typical of exam problems Brian Kernighan and Dennis Ritchie, n n – 19 – “The C Programming Language, Second Edition”, Prentice Hall, 1988 The “C” bible CMSC 313, F ‘ 10

Course Components Lectures n Higher level concepts Projects n n The heart of the course 2 or 3 weeks Provide experience writing C programs Provide in-depth understanding of an aspect of systems Exams n Test your understanding of concepts & mathematical principles l Critical component of grade – 20 – CMSC 313, F ‘ 10

Getting Help Class Web Page n n n www. cs. umbc. edu/courses/undergraduate/313/spring 11 Copies of lectures, assignments, exams, solutions Clarifications to assignments Black. Board n n n http: //blackboard. umbc. edu Clarifications to assignments, general discussion The only board your instructors will be monitoring Email n – 21 – frey@cs. umbc. edu CMSC 313, F ‘ 10

Policies: Assignments Work groups n Some projects are team of two Handins n n Assignment due time/date specified in project description Electronic handins Appealing grades n Within 7 days of completion of grading. l Following procedure described in syllabus n n – 22 – Projects: Talk to your TA Exams: Talk to your instructor CMSC 313, F ‘ 10

Timeliness Grace Days n n n 4 grace days for the course Covers scheduling crunch, out-of-town trips, illnesses, minor setbacks Save them until late in the term! Lateness Penalties n Once grace days used up, penalized 10% / “day” Catastrophic Events n n Major illness, death in family, … Work with your academic advisor to formulate plan for getting back on track Advice n – 23 – Once you start running late, it’s really hard to catch up CMSC 313, F ‘ 10

Cheating What is cheating? n n n Sharing code: either by copying, retyping, looking at, or supplying a copy of a file. Coaching: helping your friend to write a lab, line by line. Copying code from previous course or from elsewhere on WWW l Only allowed to use code we supply, or from textbook student website l What is NOT cheating? n n Explaining how to use systems or tools. Helping others with high-level design issues. Penalty for cheating: n n Zero on your project and 1 letter grade reduction in final grade You WILL be reported to the UMBC Academic Conduct Committee Detection of cheating: n n – 24 – We do check and our tools for doing this are much better than you think! Checking may be performed at any time during the semester CMSC 313, F ‘ 10

C Programming l Topics n Variables, arrays, structs n Control flow Pointers n n – 25 – Functions Multi-file programs Makefiles CMSC 313, F ‘ 10

Programs and Data Topics n n – 26 – Bits operations, arithmetic, assembly language programs, representation of C control and data structures Includes aspects of architecture and compilers CMSC 313, F ‘ 10

The Memory Hierarchy Topics n n – 27 – Memory technology, memory hierarchy, caches, disks, locality Includes aspects of architecture and OS. CMSC 313, F ‘ 10

Virtual Memory Topics n n – 28 – Virtual memory, address translation, dynamic storage allocation Includes aspects of architecture and OS CMSC 313, F ‘ 10

Processor Architecture l Topics – 29 – n A look at binary instructions n A closer look at the hardware CMSC 313, F ‘ 10

Project Rationale Each project should have a well-defined goal such as solving a puzzle or winning a contest. Doing a project should result in new skills and concepts We try to use competition in a fun and healthy way. n n n – 30 – Set a reasonable threshold for full credit. Post intermediate results on Web page for glory! Contests for extra credit CMSC 313, F ‘ 10

Good Luck! – 31 – CMSC 313, F ‘ 10