Two Stop Bitsnew | comments | tags | ask | submitlogin
  • colinlm 47 days ago | parent | on: Optimizing a 6502 image decoder, from 70 minutes t...
    Yes, it was very painful at first. The things that offset the pain is that at the start, the code was strictly the same (C code) for x86-64 and 6502, so I could iterate bugs out with the x86-64 decoder before trying with the 6502 code, in a few milliseconds. Afterwards, once I started going assembly on the 6502 code I iterated over that using MAME's Apple IIgs with 16MHz ZipChip, making the wait ~5 minutes instead of 70 at start, and less and less as I progressed.
    • bmonkey325 47 days ago
      What an amazing time to be alive where MAME is a development environment.
  • colinlm 50 days ago | parent | on: Optimizing a 6502 image decoder, from 70 minutes t...
    Thanks :) I do time the 6502 code using the MAME emulator, its debugger's trace feature, and a profiler I made. It's far from perfect (gets very confused by tricks like pha/pha/rts in the IIe ROM) but works under IIc emulation and allows me to precisely count cycles in my code: https://www.colino.net/wordpress/en/a2trace-debug-and-profil.../
lists | rss | source
Search:
Two Stop Bits is a discussion web site about retro computing and gaming.