about summary refs log tree commit diff stats
path: root/subx/examples/ex5.subx
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2019-05-12 07:36:18 -0700
committerKartik Agaram <vc@akkartik.com>2019-05-12 07:41:34 -0700
commit8c1a69089bcb0be8ee869a3f83c3151a7083e27c (patch)
tree319e3b04bb5d94b0306e336dff573d6685e8d683 /subx/examples/ex5.subx
parentd5d43e044d16335a3a865a8c9f5aea5cbad73360 (diff)
downloadmu-8c1a69089bcb0be8ee869a3f83c3151a7083e27c.tar.gz
snapshot of carry flag implementation
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
Diffstat (limited to 'subx/examples/ex5.subx')
0 files changed, 0 insertions, 0 deletions