| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
More tweaks for check passes. Ensure they're never first-class
transforms.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It would be confusing to use negative numbers in raw hex. But we'll rely
on programmer taste there.
|
| |
|
|
|
|
| |
Hacky test. I'm creating a helper to run tests just for this layer. But
I won't be able to do this when I want to selectively run just
transforms below some level.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The current approach to warnings is workable. We'll just never print
warnings to the screen in tests. In tests you can do whatever you want.
This is simpler than messing with levels of warnings.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Draft attempt at cleaning up warnings, but this isn't quite right.
We still emit warnings for every level-1 scenario, and hiding for each
of them seems painful.
Even if we do that, level-2 scenarios would want to hide level-3 and
over warnings, but *not* level-1 warnings. So we need a cardinal number
rather than booleans.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Reorganize layers in accordance with the plan in layer 29.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Syntax highlighting for dot leaders.
|
| | |
|
| | |
|
| |
|
|
| |
Better organize registration of transforms in main().
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Why the heck was I using ints for OPEN/CLOSED in the first place?!
|
| | |
|
| |
|
|
| |
ModR/M instructions actually can't contain disp16.
|
| |
|
|
|
| |
Also purge some unused helper scripts. Good ideas in theory, but no
point if they didn't make it to muscle memory.
|
| |
|
|
| |
The teensy/ examples have outlived their usefulness, I think.
|
| | |
|
| |
|
|
| |
Some debugging affordances.
|
| | |
|
| |
|
|
| |
Fix trace for the bugfix of comment 4456.
|
| |
|
|
| |
Port recent changes to build_and_test_until to subx/
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Really ugly solution.
|
| | |
|
| |
|
|
| |
Got a couple of instructions mixed up.
|
| |
|
|
| |
Keep a few macros more tightly scoped to just the transform they're used in.
|
| | |
|
| | |
|