| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
subx: now starting on subtraction instructions.
|
| |
|
|
|
|
|
|
|
| |
subx: add immediate
First example of a more complex opcode that needs to do its own decoding
to decide what instruction to run.
|
| |
|
|
|
|
| |
Fix non-standard switch statement.
|
|
|
|
| |
Start implementing core x86 addressing mode decoding.
|
|
|
|
| |
Consistent naming for the common terms 'register' and 'memory'.
|
|
|
|
|
|
| |
No, go back to a vector for `Memory`. We need it to be contiguously laid
out in memory so that we can write words all at once rather than a byte
at a time.
|
|
|
|
| |
Take control of hex byte parsing.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Make memory a sparse map rather than contiguous vector.
In the process, a bugfix for `load_program`: support multiple lines of
comments.
Also save a local copy of the x86 cheatsheet I've been using:
https://net.cs.uni-bonn.de/fileadmin/user_upload/plohmann/x86_opcode_structure_and_instruction_overview.pdf
|
|
|
|
| |
Fix CI.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|