Add the minimum number of NOP instructions to the code below so that it will run correctly on a pipeline that does not handle data hazards.

Make sure it is the minimum number of NOPs (might be 0 in between some instructions)! For example, without even thinking twice and not even looking at the code content below, I can state with confidence that adding 10 NOPs in between each instruction will solve all data hazards! The problem is then you are heavily penalizing your energy expenditure and throughput in catering to these excess NOPs in your code.

addi x11, x12, 7

add x13, x11, x12

addi x14, x11, 17

add x15, x13, x12