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

rename instructions #3

Open
vadixidav opened this issue Jul 31, 2016 · 0 comments
Open

rename instructions #3

vadixidav opened this issue Jul 31, 2016 · 0 comments

Comments

@vadixidav
Copy link
Member

vadixidav commented Jul 31, 2016

When the architecture was first created, the only intended way to interface with the DCs was by reading and writing directly from them. Once immediate instructions were created to pull from dc0 specifically, using it as a source for immediate values, the architecture now has a confusing naming convention regarding what immediate means. Many of the instructions should be renamed to reflect newer design paradigms.

All instructions which read a value from dc0 specifically and cannot be used on other DCs should be considered "immediate" instructions. Those should contain the letter 'i' in their name.

All instructions which read a value from any DC should continue to be called by their name followed by a #, indicating that the # can be replaced with 0-3 for the DC being used.

Other names (including jumps/branching) should be cleaned up according to this convention and standardized.

List:

  • Immediate instructions end with "i"
  • DC instructions end with "#"
  • Interrupt instructions begin with "int"
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

1 participant