Skip to content
This repository has been archived by the owner on Apr 27, 2023. It is now read-only.

Spec: MP Shift destination register order. #24

Closed
3 tasks
ben-marshall opened this issue Sep 26, 2018 · 1 comment
Closed
3 tasks

Spec: MP Shift destination register order. #24

ben-marshall opened this issue Sep 26, 2018 · 1 comment
Assignees
@ben-marshall @danpage
Labels
enhancement New feature or request
Projects
Implementation
Milestone
Initial Public Re...

Comments

@ben-marshall
Copy link
Member

ben-marshall commented Sep 26, 2018 •
edited

Change spec and implementation / model so that the 64 bit result is made up of:
{crs2, crs1} << shamt rather than {crs1,crs2} << shamt.

Not only is this more sensible, it makes implementation easier as well.

  • Specification
  • Model
  • Implementation
@ben-marshall ben-marshall added the enhancement New feature or request label Sep 26, 2018
@ben-marshall ben-marshall self-assigned this Sep 26, 2018
@ben-marshall ben-marshall added this to To do in Implementation via automation Sep 26, 2018
@ben-marshall ben-marshall mentioned this issue Sep 26, 2018
Closed
1 task
@ben-marshall
Copy link
Member Author

Blah. Got my registers mixed up. Ignore this.

Implementation automation moved this from To do to Done Sep 26, 2018
@ben-marshall ben-marshall added this to the Version 1.0a milestone Sep 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ben-marshall ben-marshall

@danpage danpage

Labels
enhancement New feature or request
Projects
No open projects
Implementation
  
Done
Milestone
Initial Public Release
Development

No branches or pull requests
2 participants
@ben-marshall @danpage