For this lab, you are going to write and test some assembly code using branches. As with previous assignments, in order for your solution to work with my MUnit tests, you must follow these rules:

• You must give your procedures the names indicated below.
• The procedures you write must be declared .globl.
• Use labels to access memory. (Don't use "magic" constants.)
• The method parameters will be placed in registers a0, a1, and a2. a0 will contain the first parameter, a1 the second, etc.
• Each method must end with the instruction jr $ra.
• Use the literal value 1 for true and 0 for false.

Problems

1. makes10(int a, int b) from CodingBat.

2. intMax(int a, int b, int c) from CodingBat.

3. close10(int a, int b) from CodingBat.

4. max1020(int a, int b) from CodingBat.

5. dateFashion(int you, int date) from CodingBat.

6. redTicket(int a, int b, int c) from CodingBat.

You may use this class as a starting point for your MUnit tests.

Submission and grading

Be sure to document and comment your code!

When your code passes all tests, submit the .asm file and MUnit test file using Blackboard's Assignment Manager. Call me over, and I will run your code against my tests. (Your code needs to be in the EOS environment for me to do this.)

Hints:

• To compute !a0, do the following:
  not $a0, $a0
andi $a0, $a0, 1
  (The extra andi instruction makes sure that only the least-significant bit has a value other than 0.)

For more practice

If you are looking for more assembly coding practice, consider these CodingBat problems:

• redTicket
• greenTicket
• blueTicket
• loneSum
• luckySum
• closeFar
• evenlySpaced

Updated Saturday, 13 October 2018, 3:30 PM