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.

1 files changed, 5 insertions, 2 deletions

diff --git a/032---operands.cc b/032---operands.cc
index 5203201e..5d434319 100644
--- a/032---operands.cc
+++ b/032---operands.cc
@@ -1,5 +1,4 @@
-//: Beginning of "level 2": tagging bytes with metadata around what field of
-//: an x86 instruction they're for.
+//: Metadata for fields of an x86 instruction.
 //:
 //: The x86 instruction set is variable-length, and how a byte is interpreted
 //: affects later instruction boundaries. A lot of the pain in programming
@@ -27,6 +26,10 @@ put_new(Help, "instructions",
 :(before "End Help Contents")
 cerr << "  instructions\n";
 
+:(before "Running Test Program")
+transform(p);
+if (trace_contains_errors()) return;
+
 :(code)
 void test_pack_immediate_constants() {
   run(