The table also shows the cycles per instruction and reflects the fact that our hardware includes a floating point co-processor:

If we compile the ERAU Run with the no-FP-hardware option and then measure the running time of the resultant (integer equivalent) program, we get a time of 4.25 seconds.

1. How much faster is our program when we compile with the floating point co-processor option than when we compile without it?
2. What is the average number of integer instructions being produced by the compiler to replace each floating point instruction? (Average over all FP instructions; you have no way of telling how many integer instructions to replace an FP add versus how many for an FP divide, for example.) As per the third row of the table above, continue to assume that the CPI for all integer instructions is 5
3. What is the MIPS rate of our hardware executing this integer-equivalent version of the ERAU Run?

Instruction ERAU Run Instruction Count Cycles Required Per Instruction 8 Floating point multiply or divide 7,000,000 Floating point add or subtract 12 2,000,000 All others (non floating point) 5 10,000,000 Instruction ERAU Run Instruction Count Cycles Required Per Instruction 8 Floating point multiply or divide 7,000,000 Floating point add or subtract 12 2,000,000 All others (non floating point) 5 10,000,000