# Identifying problem in MIPS pipeline datapath

I'm having trouble identifying a problem in this pipelined datapath. After executing an add instruction, there are 5 subsequent R-type instructions executed. However, we are assuming no data hazard, so no data dependencies that are relevant. That confuses me because that takes out the main issue with executing multiple R-type instructions. Could it be a structural hazard in which there's not enough resources to execute multiple instructions at the same time, thereby needing more hardware?

• After executing an add instruction … one particular R-Type (Register) instruction … there are 5 subsequent R-type instructions executed Well, should run like a charm. I'm having trouble identifying a problem in this pipelined datapath. How do you know there is one, and what do you know about it? – greybeard May 13 at 21:01
• Mentor gave me this prompt to think about, and said there is a problem. – noscreen May 13 at 21:38
• Well, are there any R-Type instructions the description of which shows something like undefined, locked*/*interlocked, stall? – greybeard May 13 at 21:49
• No, there are none. Just "5 subsequent R-type instructions." – noscreen May 13 at 21:54
• are there, as in in the machine specification, in Gerry Kane's MIPS RISC Architecture – greybeard May 13 at 21:59