5% of instructions are unconditional branches (jumps) bullet 20% of instructions are conditional branches. On average, 65% of conditional branches are taken. bullet There is no source of stalling other than stalling related to branches. An architecture with six pipeline stages and a predict-not-taken strategy calculates branch addresses for all branches during the second cycle, and condition bits for conditional branches during the third cycle. For any kind of branch (unconditional or conditional), the PC is updated at the end of the cycle in which all information needed to figure out where to go next is available How many cycles of stall are required for a jump? How many cycles of stall are required for a taken branch? What is the CPI of the code if a predict-not-taken strategy is used? 5% of instructions are unconditional branches (jumps) bullet 20% of instructions are conditional branches. On average, 65% of conditional branches are taken. bullet There is no source of stalling other than stalling related to branches. An architecture with six pipeline stages and a predict-not-taken strategy calculates branch addresses for all branches during the second cycle, and condition bits for conditional branches during the third cycle. For any kind of branch (unconditional or conditional), the PC is updated at the end of the cycle in which all information needed to figure out where to go next is available How many cycles of stall are required for a jump? How many cycles of stall are required for a taken branch? What is the CPI of the code if a predict-not-taken strategy is used