you cant know from the disk how the game would run.
this is best to see with condition jumps.
you cant know where the next jump would take you, so you cant know what instructions will come after it until you calculated the condition for jump.
thats why dolphin only recompiles until next jump, then executes code, then takes jump, starts to recompile what comes after jump... and so on.
(just explained simple, if you need more info, i think ector wrote this part)
theoretically(!!!) it would be possible to calculate 2 upcoming paths on a 3rd and 4th core and depending on what jump is taken, this path is chosen and allready recompiled.
But i have really NO idea if this would make it faster at all, as the usual parts are like ~50 instructions till next jump, as far as ive seen in debugger.
So synchro between cpu-cores must be in low nano-second time which is really fast.
Thats why i doubt its possible.
this is best to see with condition jumps.
you cant know where the next jump would take you, so you cant know what instructions will come after it until you calculated the condition for jump.
thats why dolphin only recompiles until next jump, then executes code, then takes jump, starts to recompile what comes after jump... and so on.
(just explained simple, if you need more info, i think ector wrote this part)
theoretically(!!!) it would be possible to calculate 2 upcoming paths on a 3rd and 4th core and depending on what jump is taken, this path is chosen and allready recompiled.
But i have really NO idea if this would make it faster at all, as the usual parts are like ~50 instructions till next jump, as far as ive seen in debugger.
So synchro between cpu-cores must be in low nano-second time which is really fast.
Thats why i doubt its possible.