From: Robert M. <mr...@gm...> - 2012-06-16 19:54:20
|
PPC_DECODE_CACHE enables a memory block decode_cache_p which holds up to 32768 consecutive results of decode(opcode) for a block of consecutive PPC instructions (32-bit words). There is a profiling function enabled by PPC_PROFILE_COMPILE_TIME which will record the amount of CPU time used by the decode cache function, printing "compile" vs "predecode" time vs total emulation time. I'm also prone to wonder why PPC_DECODE_CACHE was disabled by default -- it seems that if Gwenole went to all that effort implementing a decode cache (it's about 150 lines of code), why would it be disabled by default? On 6/16/12, Alexei Svitkine <ale...@gm...> wrote: > For example, let's take this commit by Tycho which kallisti5 pulled: > https://github.com/tycho/sheepshaver/commit/ceed8dca09fd5e5fe4e1bf9127d628382cb0f350 > > Presumably this makes something faster. Maybe it does, it looks plausible - > [...] -- Robert Munafo -- mrob.com Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com |