Page 1 of 1

Step 2 As you can see the exception handler does not worry about interrupts. We ignore them for now. What the handler do

Posted: Mon May 02, 2022 12:21 pm
by answerhappygod
Step 2 As You Can See The Exception Handler Does Not Worry About Interrupts We Ignore Them For Now What The Handler Do 1
Step 2 As You Can See The Exception Handler Does Not Worry About Interrupts We Ignore Them For Now What The Handler Do 1 (104.67 KiB) Viewed 39 times
Step 2 As you can see the exception handler does not worry about interrupts. We ignore them for now. What the handler does is that it only prints out a message indicating what happened and then returns. The message SPIM prints has two parts, the first part comes from the simulator itself and the second is printed within the exception handler. Write a program called lab7.1.asm which: • declares a variable called MAX_INT with the initial value the maximum value of a signed integer • loads the value of MAX_INT in register $to and adds it to itself (use signed addition) Q6: Will your program, when run, generate an exception? If you answer yes, then indicate whether it is a trap or an interrupt. Run lab7.1.asm and write down the error message you get on screen. For each line in the error message clearly indicate the source in the Source' column: use a S to indicate the message is generated inside the simulator, and a T to indicate it is generated inside the trap handler. Error message generated by lab7.1.asm Error message Source