-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
I found a bug when executing two commands MULH and MUL one after the other
This is correct result achieved by executing solo MULH operation:

This is correct result achieved by executing solo MUL operation:

And this is incorrect result when MUL goes after MULH:

It happens because control signal "is_mulh" and result of multiplication "mul_rd" performed in combinational logic.

So in 1st clock "is_mulh" already takes the value of MUL and "result" takes the value of lower part of "rd" when it have to keep value of high part

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels