Autograding is back for this assignment; but minutes are limited. Please don't use the autograder as your primary means of testing. Write your own tests and only submit at the end of lab when you are confident your tests will pass. The quality of your tests will affect your grade.

For this lab, you are going to write and test some assembly code using branches. You may want to watch first --- especially if you are in a section that meets on Wednesday.

As with previous assignments, in order for your solution to work with my MUnit tests, you must follow these rules:

• The file name must be branches.asm.
• 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.

This GitHub Classroom repository has a file you can use as the starting point for your MUnit tests.

Submission and grading

Be sure to document and comment your code!

When your code passes all tests, commit your code with [Grade Me] in the message.

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 Monday, 19 October 2020, 3:34 PM