370L20 - EECS/CS 370 Pipeline Performance Exceptions...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
EECS/CS 370 Pipeline Performance, Exceptions Lecture 20
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Next four lectures on pipelining Data hazards Control hazards Other issues: Exception handling in pipelines calculating performance Notes about the exam Exam (Friday 26Oct2001 2:30pm) Advanced topics
Background image of page 2
Exception handling Much harder with pipelined implementation Multiple instructions executing at the same time Simple Case: e.g., ALU overflow “flush the pipeline after the exception” “handle the exception” Identify exception (PC+1) in ID/EX pipeline register JALR to exception handler
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Early Exceptions What about an early (fetch) exception? Maybe a mis-speculated fetch (branch is wrong, fetching “down the wrong path”) Solution: Delay the handling of an exception until it is known to be a “real” problem. Send noops down the pipeline from the point of the exception until you are sure.
Background image of page 4
Late Exceptions What about a late (WB) exception?
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 14

370L20 - EECS/CS 370 Pipeline Performance Exceptions...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online