Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I-type instructions has a different opcodes #9

Open
Billkyriaf opened this issue Jan 15, 2024 · 3 comments
Open

I-type instructions has a different opcodes #9

Billkyriaf opened this issue Jan 15, 2024 · 3 comments
Assignees

Comments

@Billkyriaf
Copy link

In the \subsection{I Type} the first graph shows the opcode as 0000011, which is the opcode for the memory instructions. The I-Type ALU instructions have opcode 0010011, the jalr instruction has opcode 1100111 etc. In the subsection, there is no clarification for the different opcodes. I apologize if this matter is covered elsewhere. Finally, if it is not covered I suspect the same problem may occur in all the types of instructions covered in the 5.2 subsection.

@johnwinans johnwinans self-assigned this Jan 16, 2024
@johnwinans
Copy link
Owner

I am surprised that this has not come up before. I must have copied & pasted something without finishing the necessary updates.

@johnwinans
Copy link
Owner

Maybe I should just put all zeroes or Xs in the opcode field since that is not really the relevant part of the discussion at that point?

@Billkyriaf
Copy link
Author

All Xs would be good I think, to show that it is just a placeholder. But I believe it would be very useful to include the opcode, func3, and func7 next to each instruction. Chapter 5 is a great reference and it would be great if it had all the information in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants