$4\mathrm{.}30$ This exercise explores how exception handling affects pipeline design. The first three problems in this exercise refer to the following two instructions:

Which exceptions can each of these instructions trigger? For each of these exceptions, specify the pipeline stage in which it is detected.

$4\mathrm{.}30\mathrm{.}2[10]\backslash (<mi>\backslash </mi>$S $4\mathrm{.}9>\backslash )$ If there is a separate handler address for each exception, show how the pipeline organization must be changed to be able to handle this exception. You can assume that the addresses of these handlers are known when the processor is designed.

If the second instruction is fetched immediately after the first instruction, describe what happens in the pipeline when the first instruction causes the first exception you listed in Exercise $4\mathrm{.}30\mathrm{.}1.$ Show the pipeline execution diagram from the time the first instruction is fetched until the time the first instruction of the exception handler is completed.

In vectored exception handling, the table of exception handler addresses is in data memory at a known $($fixed$)$ address. Change the pipeline to implement this exception handling mechanism. Repeat Exercise $4\mathrm{.}30\mathrm{.}3$ using this modified pipeline and vectored exception handling.

$4\mathrm{.}30\mathrm{.}5[15]\backslash (<mi>\backslash </mi>$S $4\mathrm{.}9>\backslash )$ We want to emulate vectored exception handling $($described in Exercise $4\mathrm{.}30\mathrm{.}4)$ on a machine that has only one fixed handler address. Write the code that should be at that fixed address. Hint: this code should identify the exception, get the right address from the exception vector table, and transfer execution to that handler.