Talk:Hazard (computer architecture)

Latest comment: 9 years ago by Kotz in topic anti

too technical in "forwarding"

edit

The 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)Reply

--202.65.209.210 (talk) 02:38, 16 October 2009 (UTC)Reply

WAW - Write After Write

edit

I 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)Reply

Sources

edit

This book is one of most reliable sources in CPU architecture and Hazards. `a5b (talk) 20:45, 12 August 2012 (UTC)Reply

  • Patterson, David A.; Hennessey, John L., Computer Organization and Design (4 ed.), Morgan Kaufmann, p. 336

Structural or Functional?

edit

CQ-AQA fifth edition uses Functional Hazard. — Preceding unsigned comment added by Olsonist (talkcontribs) 22:26, 21 November 2012 (UTC)Reply

anti

edit

The term "anti-dependency" should be explained, I think. Kotz (talk) 07:52, 23 July 2015 (UTC)Reply

Should a brief statement be added to underscore RAR (read after read) is not a hazard case (for completeness?)