Closed GoogleCodeExporter closed 8 years ago
huh, or did I not think things through... shouldn't the condition check the
real row number? *wonders*
Original comment by danny.m...@gmail.com
on 26 Jun 2011 at 9:04
two comments about speed..
looking at the above profile, mmu.xread_read_memory seems quite slow, because
of the for loop in there. it looks like it should be possible to work around
that..
you can make the C64 emulator use multiple cores :-) that is, the boehm GC can
make use of those.. using 7.2 can also help a lot in some cases (6.8 is usually
installed on distributions). ./configure --enable-cplusplus
--enable-large-config --enable-parallel-mark --enable-thread-local-alloc
--enable-threads=pthreads.
just some thoughts, I'm bored at work.. :-)
Original comment by mark.duf...@gmail.com
on 28 Jun 2011 at 10:39
Yeah, I've thought about just hard-coding all the special non-RAM mmu things
instead of the "for" loop like the CIA, VIC, SID, CIA2 and CPUPort now.
However, it would also be possible to limit the ability of set_overlay a bit
(i.e. which addresses are allowed in an overlay) and use a regular array to
look up what is to be done. I think the latter would be no problem since all
the addresses are in pages of 256 bytes each on the original C64 in the first
place, so there are only 256 possibilities max after a simple bit shift
"address >> 8"...
Yeah, I've got boehm GC 6.8 installed as well. Good to know the newer GC
supports multicore better ^^
Original comment by danny.m...@gmail.com
on 29 Jun 2011 at 7:27
Original issue reported on code.google.com by
danny.m...@gmail.com
on 15 Oct 2010 at 9:34Attachments: