[issue4714] print opcode stats at the end of pybench runs

Change by Guido van Rossum : -- resolution: -> out of date stage: patch review -> resolved status: languishing -> closed ___ Python tracker ___

[issue4714] print opcode stats at the end of pybench runs

Mark Lawrence added the comment: @Antoine/Marc-Andre are either of you interested in taking this forward? -- nosy: +BreamoreBoy ___ Python tracker ___

[issue4714] print opcode stats at the end of pybench runs

Changes by Mark Lawrence : -- status: open -> languishing versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___ Python-bugs-list

[issue4714] print opcode stats at the end of pybench runs

Antoine Pitrou added the comment: > I don't think it's worth doing this for low-level and highly > artificial benchmarks like the ones run by pybench. Well, it can help to know which opcodes are executed when running a particular bunch of sub-tests :) > If at all, then opcode statistics should

[issue4714] print opcode stats at the end of pybench runs

Marc-Andre Lemburg added the comment: On 2008-12-21 22:37, Antoine Pitrou wrote: > New submission from Antoine Pitrou : > > This patch prints opcode statistics at the end of a pybench run if > DYNAMIC_EXECUTION_PROFILE has been enabled when compiling the interpreter. > > Is it ok? Is it better

[issue4714] print opcode stats at the end of pybench runs

New submission from Antoine Pitrou : This patch prints opcode statistics at the end of a pybench run if DYNAMIC_EXECUTION_PROFILE has been enabled when compiling the interpreter. Is it ok? Is it better to add it to the Benchmark class? -- components: Demos and Tools files: pybench-opcod