Re: [hatari-devel] Hatari profiler updates and CPU cycle questions

[Douglas Little <doug694@xxxxxxxxxxxxxx>]

Hi Laurent,

When you trace your program (ie, the program is running with the registers in the good state), the cycles for this instruction will display [04 cycles] if X memory w< $200 or [05 cycles] if X memory is > $200

So, while executing your code, the value was always [04 cycles] (as you said X is always in the internal memory) and Eero's profiler is good.

Ok I just misunderstood the meaning of the (05 cyc) estimate - it is a 'worst' case estimate *including* any potential penalties, and not the time for the instruction and EA on its own? (i.e. penalties must be added). 

In that case the values do make sense and it must be correct yes.

D.