robfinch wrote:
That 68k code is pretty impressive.
...and sometimes you win the staring competition with the abyss.
I haven't gotten as far as testing it yet, but after waving my fist at it for most of Saturday I am pretty confident I got it down to 66 bytes. That is still with a 2-byte penalty for the format being small-endian and a 4-byte penalty for not using 68020+.
Optimizing for size can be detrimental to optimizing for speed; with more common code executed you can be sure to have known (beneficial) states.