dml wrote:There is no code/rendering profiler in BM. This would have been a good move - seeing the %age impact of various kinds of drawing and relative use, for guiding sensible optimisation effort. A prime-number based TimerC event sampler coupled with a task index updated in the main code would be enough to build a decent picture over a few seconds and quite easy to implement.
No need to implement that in BM, Hatari debugger includes a profiler, and it supports both CPU and DSP side as well:
http://hg.tuxfamily.org/mercurialroot/h ... e_debugger
If you load DSP symbol address information to the debugger, it can also show how many times certain symbols get called, or a trace of how the symbols get called.