|Re: [hatari-devel] Hatari profiler updates and CPU cycle questions|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
On torstai 31 tammikuu 2013, Douglas Little wrote:
> On 31 January 2013 15:55, Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:
> > For DSP I could store (in addition of sum of instructions & cycles)
> > also min and max cycle values for individual addresses. Disassembly
> > could them contain those, or just indicator that they differed.
> > Would that be enough?
> That would be great yes. Min/max provide more detail, but take more space
> per line... (I suppose a full export would be best served with min/max
> since it can be post-processed into anything beyond that point).
Ok, I'll check that. I've commited some fixes to TOS/CART area
accounting (when one doesn't give symbols for those).
For me the symbol data seems completely sane, at least for TEXT
stuff, but I'm relying on "nm" output of GCC & VBCC Vasm built
> One more note: having an identifiable prefix/delimiter before each
> profiler numeric column e.g. "@:" (or whatever works!) makes it easier
> to extract those columns into Excel or other tools.* A minor thing - I
> may just apply my own patch for that since it can again be
grep '([0-9]\+,' profile.txt
Neither CPU nor DSP disassembly should contain that pattern.