| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
I'd been planning next to automatically namespace jump targets in
different functions. But just a check for duplicate labels should
suffice, and managing unique names isn't a huge burden. I'm wary of
growing the translator too much. All this will eventually need to be
self-hosted in SubX.
|
| |
|
|
|
|
|
|
|
| |
Targets you can jump to and ones you can call are conceptually disjoint
sets.
I'm highlighting these in Vim, but it's a pretty complex pattern.
Arguably errors shouldn't be highlighted. Only warnings that are easy to
be accidentally deployed.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
I found a bug with multiply in the process; another case (after the swap
of call/jump opcodes in 4453) where there's no point improving testing.
Unit tests can only tell us if our instructions are internally
consistent. Validating against a real machine has to be manual.
I'm definitely feeling the pain of debugging machine code now, that's
for sure. Going over an instruction trace, comparing the state of
registers line by line.
|