diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2017-04-06 09:51:00 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2017-04-06 09:51:00 -0700 |
| commit | e317da73b02d2d0e4d62584c93ed31126bb545ca (patch) | |
| tree | 91e8d6c92e257ae9c214a5bac8ca82534b66d083 | |
| parent | 5b96e723f17681368900dd817bfff7d11ef55b9a (diff) | |
| download | mu-e317da73b02d2d0e4d62584c93ed31126bb545ca.tar.gz | |
3814
Initial baby steps at trying to understand why rendering to screen is so slow in Mu. I'd forgotten about this old "poor man's profiler" I'd added back in 2015.
| -rw-r--r-- | 020run.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/020run.cc b/020run.cc index e760deaa..39168588 100644 --- a/020run.cc +++ b/020run.cc @@ -65,6 +65,7 @@ void run(const recipe_ordinal r) { void run_current_routine() { while (should_continue_running(Current_routine)) { // beware: may modify Current_routine // Running One Instruction +//? Instructions_running[current_recipe_name()]++; if (current_instruction().is_label) { ++current_step_index(); continue; } trace(Initial_callstack_depth + Trace_stream->callstack_depth, "run") << to_string(current_instruction()) << end(); if (get_or_insert(Memory, 0) != 0) { |