FINAL TUE DEC 21 8a OS407
• study guide : txt

MON NOV 29
• microprocessor report : pdf
• pentium history html

MON NOV 22
• assignment 11: performance lab
handout pdf
files tar
due Fri Dec 10

WED NOV 15
• assignment 10: cache memory exercises pdf
due Wed Nov 22

MON NOV 8
• assignment 9: archlab part C
due Mon Nov 15

FRI OCT 22 MIDTERM
• study notes txt

FRI OCT 15
• assignment 8: archlab parts A and B
due Wed Oct 27
    tar
    sum.ys starter file
    pdf handout

FRI OCT 1
• assignment 6: x86 ISA html due Oct 8
• assignment 7: bomblab pdf due Oct 15
  readme txt
  gdb notes pdf

FRI SEP 24
• assignment 5: HC11 memory lab pdf files zip
• schematic hints pdf
• appendix b pdf
• cypress 6264 pdf
due Oct 1

MON SEP 20
• assignment 4: conversions, branching, the stack pdf
due Sep 24

FRI SEP 17
• assignment 3: HC11 beep lab pdf files zip
due Sep 24

FRI SEP 10
• assignment 2: HC11 boot lab pdf files zip
due Sep 17
• hardware pic jpg
• java setup html
• as6811 assembler as6811.exe docs
• intro to 6811 pdf
• m68hc11e manual pdf
• uml305dev manual pdf
• uml305dev checkout pdf

WED SEP 8
• assignment 1: historic computer html due Sep 10

91.305 Assignment 6:
The x86 Instruction Set and C-Language Compilation

Reading and Practice Problems

Read the following from Bryant and O’Hallaron, Chapter 3. Do the practice problems as indicated for each section.

• Introduction (pp. 124–125)
• 3.1, Historical Perspective (pp. 125–128).
• 3.2, Program Encodings (pp. 128–134).
• 3.3, Data Formats (pp. 135).
• 3.4, Accessing Information (pp. 136–143); Practice Problems 3.1 and 3.2.
• 3.5, Arithmetic and Logical Operations (pp. 143–148); Practice Problem 3.6.
• 3.6, Control (pp. 148–170); Practice Problem 3.12.

Since answers are given in the book, the practice problems are done on the honor system. Basically, you should make an effort to solve them, and then use the solutions as necessary to confirm your understanding.

Some of the practice problems (e.g., 3.2) suggest that you actually sit down in front of a Linux machine, type in some C code, compile it (using the -S switch, which generates the assembly), and examine the result.

I highly recommend that you actually do this. It's a lot more interesting when you can see the gcc compiler at work. If you don't have an x86-based Linux machine of your own, log into one of the department’s machines (e.g., mercury) to do this.

To Turn In

Please turn in written solutions (prepared individually) for the following homework problems (starting on page 231 of the text).

It’s perfectly acceptable (or should I say, encouraged!) to type in C code and compile it (with -S) to help figure out the answers!

• 3.31
• 3.32
• 3.33