Skip to content

CSR instructions should treat immediate as unsigned #9

Description

@MichaelBell

e.g. InstructionCSRRW(x1, x0, csrnames.cycle) raises an error because csrnames.cycle isn't in the valid range. I have worked around this by subtracting 0x1000 from the constant.

I think there should be a variant of the InstructionIType that treats the immediate as unsigned, used for the CSR instructions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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