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 /013update_operation.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 '013update_operation.cc')
-rw-r--r-- | 013update_operation.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/013update_operation.cc b/013update_operation.cc index 8366439d..c5a736f6 100644 --- a/013update_operation.cc +++ b/013update_operation.cc @@ -6,7 +6,7 @@ Transform.push_back(update_instruction_operations); // idempotent :(code) void update_instruction_operations(const recipe_ordinal r) { - trace(9991, "transform") << "--- compute instruction operations for recipe " << get(Recipe, r).name << end(); + trace(101, "transform") << "--- compute instruction operations for recipe " << get(Recipe, r).name << end(); recipe& caller = get(Recipe, r); //? cerr << "--- compute instruction operations for recipe " << caller.name << '\n'; for (int index = 0; index < SIZE(caller.steps); ++index) { |