diff options
| author | Kartik Agaram <vc@akkartik.com> | 2020-01-02 01:28:24 -0800 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2020-01-02 01:28:24 -0800 |
| commit | d02aa9ac0b9e1130ffcd5a27aa1304e80eee08d9 (patch) | |
| tree | bf592fba4275002cbbde420cef8c806bb9b1b45f /010---vm.cc | |
| parent | 01013f2ad2132dd945c6ceb168b85dc52e18882c (diff) | |
| download | mu-d02aa9ac0b9e1130ffcd5a27aa1304e80eee08d9.tar.gz | |
5863
Just clarified for myself why `subx translate` and `subx run` need to share code: emulation supports the tests first and foremost. In the process we clean up our architecture for levels of layers. It's a good idea but unused once we reconceive of "level 1" as just part of the test harness.
Diffstat (limited to '010---vm.cc')
| -rw-r--r-- | 010---vm.cc | 10 |
1 files changed, 2 insertions, 8 deletions
diff --git a/010---vm.cc b/010---vm.cc index 6675cab9..d67667f7 100644 --- a/010---vm.cc +++ b/010---vm.cc @@ -1,11 +1,5 @@ -//: Core data structures for simulating the SubX VM (subset of an x86 processor) -//: -//: At the lowest level ("level 1") of abstraction, SubX executes x86 -//: instructions provided in the form of an array of bytes, loaded into memory -//: starting at a specific address. -//: -//: SubX is fundamentally a translator. But having a VM to execute its -//: translations affords greater confidence in it. +//: Core data structures for simulating the SubX VM (subset of an x86 processor), +//: either in tests or debug aids. //:: registers //: assume segment registers are hard-coded to 0 |