akkartik
/
mu
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
mu/examples
History
Kartik Agaram 6e1eeeebfb 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
..
Readme.md 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex1 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex1.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex2 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex2.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex3 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex3.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex4 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex4.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex5 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex5.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex6 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex6.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex7 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex7.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex8 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex8.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex9 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex9.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex10 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex10.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex11 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex11.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex12 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00
ex12.subx 5485 - promote SubX to top-level 2019-07-27 17:47:59 -07:00

Readme.md

Small example programs, each with a simple pedagogical goal.

They also help to validate SubX instruction semantics against native x86 hardware. For example, loading a single byte to a register would for some time clear the rest of the register. This behavior was internally consistent with unit tests. It took running an example binary natively to catch the discrepancy.