Are WAW and WAR hazards unique to RISC processors?

  • Thread starter Thread starter user366312
  • Start date Start date
AI Thread Summary
WAW (Write After Write) and WAR (Write After Read) hazards are not exclusive to RISC processors; they can also occur in CISC architectures. These hazards arise from pipeline processing, which is present in both RISC and CISC designs. While RISC processors, such as MIPS, are often discussed in relation to these hazards, any pipeline architecture that modifies data across multiple stages can experience them. In non-pipelined systems, WAW, WAR, and RAW (Read After Write) issues may still occur but would typically be managed through software resource arbitration rather than hardware mechanisms.
user366312
Gold Member
Messages
88
Reaction score
3
TL;DR Summary
Whenever I find something on hazard, I find it in the context of RISC processors like MIPS.
Are WAW and WAR hazards unique to RISC processors?

Or, CISCs can also encounter those hazards?
 
Technology news on Phys.org
You get this hazards with any pipeline architecture that can modify data in more than one stage.
 
user366312 said:
Summary: Whenever I find something on hazard, I find it in the context of RISC processors like MIPS.

Are WAW and WAR hazards unique to RISC processors?

Or, CISCs can also encounter those hazards?
In my experience a data hazard can be encountered on CISC as well as RISC processors.
 
CPU hazards are the result of pipeline processing - either CISC or RISC. If there is no pipe-lining, you might still run into WAW, WAR, and RAW issues, but they would be handled in the software as resource arbitration issues.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Thread 'Project Documentation'
Trying to package up a small bank account manager project that I have been tempering on for a while. One that is certainly worth something to me. Although I have created methods to whip up quick documents with all fields and properties. I would like something better to reference in order to express the mechanical functions. It is unclear to me about any standardized format for code documentation that exists. I have tried object orientated diagrams with shapes to try and express the...
Back
Top