diff options
| author | Kartik Agaram <vc@akkartik.com> | 2019-02-25 00:17:46 -0800 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2019-02-25 01:50:53 -0800 |
| commit | c442a5ad806b6cccbb3ec4c5744b14b0c1f31a01 (patch) | |
| tree | 318fb1d56e7ee3c750635d3326ad0739dfdacefe /subx/032check_operand_bounds.cc | |
| parent | e5998f74ac29bb4bf2aedfdd6fbea801ffdb08f6 (diff) | |
| download | mu-c442a5ad806b6cccbb3ec4c5744b14b0c1f31a01.tar.gz | |
4987 - support `browse_trace` tool in SubX
I've extracted it into a separate binary, independent of my Mu prototype. I also cleaned up my tracing layer to be a little nicer. Major improvements: - Realized that incremental tracing really ought to be the default. And to minimize printing traces to screen. - Finally figured out how to combine layers and call stack frames in a single dimension of depth. The answer: optimize for the experience of `browse_trace`. Instructions occupy a range of depths based on their call stack frame, and minor details of an instruction lie one level deeper in each case. Other than that, I spent some time adjusting levels everywhere to make `browse_trace` useful.
Diffstat (limited to 'subx/032check_operand_bounds.cc')
| -rw-r--r-- | subx/032check_operand_bounds.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/subx/032check_operand_bounds.cc b/subx/032check_operand_bounds.cc index b2276a8c..58b7c7b9 100644 --- a/subx/032check_operand_bounds.cc +++ b/subx/032check_operand_bounds.cc @@ -27,7 +27,7 @@ check_operand_bounds(code); if (trace_contains_errors()) return; :(code) void check_operand_bounds(const segment& code) { - trace(99, "transform") << "-- check operand bounds" << end(); + trace(3, "transform") << "-- check operand bounds" << end(); for (int i = 0; i < SIZE(code.lines); ++i) { const line& inst = code.lines.at(i); for (int j = first_operand(inst); j < SIZE(inst.words); ++j) |