Skip to content

Bug  #3

@ShevtsovNikita

Description

@ShevtsovNikita

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:
image

This is correct result achieved by executing solo MUL operation:
image

And this is incorrect result when MUL goes after MULH:
image

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

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
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions