NOTE: Instructions for linux only
- To install qtspim: Run assignment_1/install.sh (this downloads the linux-x64 debian package from sourceforge and installs it)
- To install spim/xspim, run
$ sudo apt install spim
- xspim should successfully run with
$ xspim
.
If all this does is print a font name and quit, as below,
$ xspim
*-courier-medium-r-normal--12-*-75-*
run it with $ xspim -font 6x10
Assembler directives
System calls
Calling convention
- Write a program to add the integers 1 and 2
- Write a program to load and add two 32-bit values: 0x10000001 and 0x20000002.
-
- Step through the instructions
- Set an appropriate breakpoint in the program
- open qtspim ($ qtspim) → File → Reinitialize and load file → assignment_1/add1.asm → Run → see the highlighted registers on the left → celebrate.
- File → reinitialize and load file → assignment_1/add2.asm → Run → same
- File → reinitialize and load file → assignment_1/add2.asm
- find the thing that says "single step" when you hover over it. click it. as many times as you want
- reinitialize again with assignment_1/add2.asm → right click on the line that says "lui $t1, 0x1000 # temporary..." → set breakpoint → Run → see breakpoint dialog → rejoice → single step/continue
- Write a program to compute GCD of two 32-bit integers using Euclid's algorithm
- Implement the given sample program (assignment_2/sample.asm). Study the instructions and the working of the program.
- Statically declare some prompt strings for user input, and redo the addition program in assignment 1 to prompt the user for two numbers and print the result.
- Define an array of 8 integers as static data. Use the
.align
assembler directive. Read 8 values as input with prompts to the user and store it in the array. Examine what happens without the assembler directive.
- assignment_2/gcd.asm
- The sample program takes a number and counts down from it.
- assignment_2/add.asm
- assignment_2/array.asm
- Even without the
.align
directive, data is still properly aligned on word boundary; thus the program works correctly. - However, explicitly turning off alignment with
.align 0
causes address errors due to unaligned addresses.
- Even without the
- Write a function to merge two sorted arrays into another, assuming the final array has enough space. Take array1, length1, array2, length2, final_array as inputs. Call this function from main with the two halves of a length 8 array input by the user.
- Write a program for recursively calculating the factorial of an integer.
- Write a recursive mergesort procedure using the merge function taking the starting address and the length of the sub-array as arguments. It should also check that the sub-array is sorted before returning. Call this function from main with a length 8 array input by the user.
- Insert a breakpoint at a place in your code where the stack depth (wrt call activations) will be at its maximum size. Point out the various call activation records and explain the contents of the stack.
- assignment_3/merge.asm
- assignment_3/factorial.asm
- assignment_3/mergesort.asm
- Break at line 94 in mergesort.asm, since this is the point just before
mergesort(arr, 1)
returns. The call stack for each function looks like this:
↑ low addrs
+---------+ \
| s2 | |
+---------+ | ↑ low addrs
| s1 | |
+---------+ | +-----------------------------+
| s0 | | | frame for mergesort(arr, 1) |
+---------+ +- stack frame --+ +-----------------------------+
| ra | | | | frame for mergesort(arr, 2) |
+---------+ | | +-----------------------------+
| a0 | | | | frame for mergesort(arr, 4) |
+---------+ | | +-----------------------------+
| a1 | | +-->| frame for mergesort(arr, 8) |
+---------+ / +-----------------------------+
↓ high addrs
where each part represents a saved register. This is pushed on the stack for each function as it gets called. After a function returns, it's portion of the stack gets popped off. Keep in mind that the stack grows towards low addresses.