[hatari-devel] Profiling support to Hatari debugger
Eero Tamminen
eerot at users.berlios.de
Tue Jun 29 14:35:01 CEST 2010
Hi,
On Saturday 26 June 2010, Eero Tamminen wrote:
> Attached patch adds profiling information to the disassembly output.
...
> Does that look OK?
As there were no comments, I added this as-is to the repo.
Here's an example of what the profiler output looks for DSP.
It's for an idling Falcon "Virtual City" demo:
-----------
DSP profile statistics (0x0-0xFFFF):
- active address range:
0x004e-0x00c3
- active instruction addresses:
86
- executed instructions:
101279562
- used cycles:
707895386
- address with most cycles:
0x004e, 642239526 cycles (90.73% of all)
- address with most hits:
0x004e, 91749434 hits (90.59% of all)
CPU=$30e66, VBL=3301, FrameCycles=88, HBL=0, LineCycles=88, DSP=$4e
> dspprofile cycles 100
addr: cycles:
0x004e 90.73% 642239526
0x00a7 4.99% 35358807
0x009f 0.74% 5219320
...
0x009b 0.00% 880
86 DSP addresses listed.
> dspdisasm 0x004b
DSP disasm 0x4b-0x53:
004b: 64f400 000520 (04 cyc) move #0x000520,r4
004d: 0502a4 (02 cyc) movec #0x02,m4
91749434/642239526 times/cycles:
004e: 0aa980 00004e (07 cyc) jclr #0,x:0xffe9,p:0x004e
6512/45584 times/cycles:
0050: 08582b (05 cyc) movep x:0xffeb,n0
6512/32560 times/cycles:
0051: 0ad800 000056 (06 cyc) jclr #0,n0,p:0x0056
-----------
Btw. Should I show percentage of used cycles/counts also in the disassembly
output?
- Eero
More information about the hatari-devel
mailing list