ASU CSE 212 Computer Organization

https://www.youtube.com/watch?v=XomjdGFPQT0

Pat Gelsinger's Commencement Address: Congratulations Class of 2021 Intel CEO Pat Gelsinger delivers a virtual commencement speech to inspire the graduating class of 2021 – students who have spent most of the past two school ...

Final year work marks are uploaded on the SIS. Please revise your mark and ensure that the **total** of midterm and student activity is greater than or equal the total announced in the last upload sheet on microsoft teams.
You have till today Sunday 7.00 pm to report any issues you find in ** facebook message to this PAGE **. Any requests after that time will not be considered.

- Please note the Bonus given by the Dr is not added yet since it ends at the day of the exam.
- Attendance was announced with Midterm grade and we asked you to review it and it had a deadline. We will not be adjusting any attendance marks.
- Remember that in your finals exam, you are not allowed to write pseudo-instructions in any given problems unless instructed clearly in the question.
- Regarding the bonus:
* Attached the output of the grader and a sample application for the testcase provided in the pdf.
* Please note that we only evaluate the function EVAL (the one you submitted in the textbox) and not your main code.
* The code must make use of the parameters as given in registers $a0:$a3 and return the outputs in $v0-$v1 per the function convention. Passing parameters in other registers is not acceptable. The function must also preserve registers $s0:$s7 content.
* Those who failed all tests were given one mark for participation.
* The output of grader explained:
#-1 means the function produced a runtime error, happens mostly because of wrong memory address access due to improper use of registers other than the $a* registers. Which resulted in accessing a location not dividable by 4. Other errors include not preserving $ra value and thus preventing the code from returning to the main and thus timeout. One other mistake was having an overflow in code due to wrong calculations, the grader code runs before calling the function and is written in assembly and ran inside mars, that means given that the grader didn't throw an arithmetic overflow, your code shouldn't.
#1* means the code didn't return the correct $v1 and is split as following:
#10 program failed the operation a (we check the memory for these values, so failure to store in correct place will stop you here)
#11 program failed the operation b
#12 program failed the operation c
#13 program failed the operation z
#1 program saved all 4 operations correctly but didn't return it correctly
#2 program failed the sign part (s), most common case the use of improper of branch control.
#3 program failed to store the operations a,b,c,z in memory. (it passed the return so the evaluation of the memory part is delayed to this step.)
#4 program failed to preserve the values of the $s0:$s7 registers
Success: program ran correctly.
**sample main code: http://bit.ly/2N6wRpm
**output of grader: http://bit.ly/3u4yDbw