Hi Toni,
Yes, I know div/mul algo are not known on 68020/68030.
I was just thinking about a general improvement of the cycles counting
with memory access.
I think that memory access are not taken into account in 68030 mode (or
wrongly taken into acount).
I mean actually, hatari reads a movem.l (a6)+,d0-a4 in 16 cycles instead
of about 120 cycles.
I would love to see my falcon reading all this memory in 16 cycles.
I think the memory access is not taken into account for MOVEM.
I know there's still a lot of work to do to reach a better accurate
68030, but here, I was speaking of trying to reach a closer level of
accuracy (we start from far with movem ;)