Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Hazard (computer architecture)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Problems with the instruction pipeline in central processing unit (CPU) microarchitectures}} {{More citations needed|date=January 2014}} In the domain of [[central processing unit]] (CPU) [[CPU design|design]], '''hazards''' are problems with the [[instruction pipeline]] in CPU [[microarchitecture]]s when the next instruction cannot execute in the following clock cycle,{{sfn|Patterson|Hennessy|2009|p=335}} and can potentially lead to incorrect computation results. Three common types of hazards are data hazards, structural hazards, and control hazards (branching hazards).{{sfn|Patterson|Hennessy|2009|pp=335-343}} There are several methods used to deal with hazards, including [[pipeline stall]]s/pipeline bubbling, [[#Operand forwarding|operand forwarding]], and in the case of [[out-of-order execution]], the [[scoreboarding]] method and the [[Tomasulo algorithm]].
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)