| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 4475 | Kartik Agaram | 2018-08-04 | 1 | -26/+0 |
| | | |||||
| * | 4472 - experiment: help read the long lines | Kartik Agaram | 2018-08-04 | 1 | -25/+25 |
| | | |||||
| * | 4467 | Kartik Agaram | 2018-08-03 | 1 | -28/+28 |
| | | |||||
| * | 4465 | Kartik Agaram | 2018-07-30 | 1 | -2/+2 |
| | | |||||
| * | 4456 - example with function calls: factorial | Kartik Agaram | 2018-07-30 | 1 | -0/+90 |
| 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. | |||||