theperkinrex / armescpu_old_rust Goto Github PK

This is so there's no need for an OUTB and OUTR, it'd be just OUT br or OUT $0

That would make it a binary file. Or maybe only store them as hex instead of binary.
The files could have a header, like the one they have right now, that specifies the address length and data length.
Something like:

!4:8

And then the data, read be the lengths specified

This is so that there can be more instructions (because now instead of 4 bits, they're a byte long), and ram addresses can be 1 byte long instead of 4 bits.
Benefits:

• 15 -> 255 instructions
• 15 -> 255 RAM addresses
  Drawbacks:
• Rewriting the code
• Instructions now occupy 2 RAM addresses instead of 1

This would add portability, and, if the CPU is ported to rust, it would be easier.

That memory could be loaded and stored in a .mmap file

As rust is a compiled language, the CPU would run much faster than with an interpreted language like python