Re: [hatari-devel] Profiler / disassembly tests for Hatari

[Thomas Huth <th.huth@xxxxxxxxx>]

Am Sat, 1 Nov 2025 02:17:25 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:

> Hi Nicolas/Thomas,
> 
> WinUAE CPU core disassembly wrapper did not work at all (it ignored the 
> provided FILE*) which I've now fixed:
> https://www.atari-forum.com/viewtopic.php?p=487749#p487749
> 
> This isn't the first time disassembly output causes problems for 
> profiling, so I though to add tests for it.
> 
> Those tests work locally now, and they also validate that symbol 
> handling & breakpoint chaining (used for profiling) do work.  They work 
> by comparing disassembly output with profiling information, against 
> output saved to Git.
> 
> (Tests run "cyccheck.prg" from the "cycles" test, as that was 
> unstripped, unlike most other test binaries.)
> 
> However, I'm wondering whether disassembly outputs [1] (e.g. cycle 
> counts in them) would change often enough to be nuisance...
> 
> I.e. how often you'd think there will be changes to:
> * This test program
> * Handling of interrupts used by FakeTOS
> * WinUAE CPU core disassembly output format
> * 68000 & 030+MMU cycle counts
> ?

I'd maybe skip the test for anything that is not using a plain 68000 in
that case, since we know that there is no cycle-accurate 68030 emulation
yet, so I'd expect that this will change a lot during the course of time.

 Thomas