Re: [hatari-devel] Profiler question |
[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]
What format are you using to import symbols?There are two - one can load the symbols direct from the PRG/TOS if the file was built with GST/DRI (?) format. This did workwell for me from Devpac, I'm not sure I tried it with VASM, since I really only used VASM to generate GCC ".a" format linkables to use with a C project...
I don't think that means your code has 100% miss rate. It just means the profiler was able to account for all of the misses which did occur, based on cross-referenced sums.. I'm sure you can ignore it (ask Eero for details).
It's better to experiment first with the raw profiled disassembly listing to get a feel for whats happening.
It's certainly possible the symbols are not properly 'rebased' relative to your text section. This will cause them all to have wrong addresses (See my notes above)..
The fact you are getting DC.W disassembly for the hottest addresses is very strange! This would normally only happen if the memory is being reused by more than one bit of code and/or data. The profiler is a static process which monitors activity at fixed addresses - it expects code remains in one place, and is not replaced or moved after it executes.
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |