This is the talk page for discussing improvements to the Hazard (computer architecture) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||
|
too technical in "forwarding"
editThe last paragraph refers to details like a textbook, and is totally without context. It can't be understood from reading what precedes, and isn't itself linked to helpful definitions. Długosz (talk) 15:36, 31 August 2009 (UTC)
WAW - Write After Write
editI think renaming the register in i2 should be a solution. If somebody thinks so, please, edit the text. Zbytovsky (talk) 22:25, 8 February 2010 (UTC)
Sources
editThis book is one of most reliable sources in CPU architecture and Hazards. `a5b (talk) 20:45, 12 August 2012 (UTC)
- Patterson, David A.; Hennessey, John L., Computer Organization and Design (4 ed.), Morgan Kaufmann, p. 336
Structural or Functional?
editCQ-AQA fifth edition uses Functional Hazard. — Preceding unsigned comment added by Olsonist (talk • contribs) 22:26, 21 November 2012 (UTC)
anti
editThe term "anti-dependency" should be explained, I think. Kotz (talk) 07:52, 23 July 2015 (UTC)
RAR
editShould a brief statement be added to underscore RAR (read after read) is not a hazard case (for completeness?)