Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR experiments with adding an
opcode
executor which provides a count of the opcodes executed during the benchmark.TL;DR: It should be possible to provide a count of the opcodes for the subject only.
Counting Opcodes
Including Opcodes alongside the regular results
Would be possible to add a new
CompositeExecutor
which ran a set of executors. I.e. to execute the opcode executor and the regular executor.Pre and post optimisation
By using the
CompositeExecutor
it would be possible to run two instances of the Opcode executor, one for unoptimised and one with optimised results.Debugging Opcodes
It would also be good to add a convenience command to debug the opcodes. However, I cannot see a way to separate the signal from the noise. The opcodes are not presented in the order that would make this possible.