| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | snapshot of carry flag implementation | Kartik Agaram | 2019-05-12 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | Tests failing. This approach seems wrong. I'm not sure even the tests are correct. Also, some open questions: 1. Should setting the overflow flag always set the carry flag? 2. Should the carry flag only be set on add/subtract/compare, or by all arithmetic ops? 3. Had to turn off the -ftrapv flag in `build`. Is there a way to detect overflow without actually causing overflow? Once we start setting CF correctly we have to implement jump above/below instructions (8- and 32-bit displacement variants). https://github.com/akkartik/mu/issues/30 | ||||
| * | 4970 | Kartik Agaram | 2019-02-15 | 1 | -4/+4 |
| | | |||||
| * | 4403 | Kartik Agaram | 2018-07-25 | 1 | -0/+2 |
| | | | | | | | Couple of improvements for the tangle/ directory: a) Start running tangle unit tests at build time again. b) Option to print out test names as they run, just like in top-level. | ||||
| * | 4288 | Kartik Agaram | 2018-06-28 | 1 | -0/+1 |
| | | | | | Give subx too the recent support for running a single test. | ||||
| * | 4013 | Kartik K. Agaram | 2017-10-11 | 1 | -3/+3 |
| | | |||||
| * | 3930 - experimental bytecode interpreter | Kartik K. Agaram | 2017-06-19 | 1 | -0/+106 |