I've been working on JIT core improvements for a while now but they have never seen the light of day since I haven't felt they were up to snuff or fully completed. There are quite a lot of changes in the pipeline for these JIT core improvements.
This is the first step on the road to the JIT improvements.
From a technical standpoint of this change, what it changes is that it improves our CPU block sizes by compiling through conditional branching instructions. This improves speed in the JIT recompiler since we stop bouncing back and forth from JIT code and our JIT dispatcher as often.

From my amount of benchmarking I've seen improvements from 0% to 11% CPU speed improvements.
I've tested the povray bench a couple of times. Without the changes I got these results {10:42, 10:34}. With the changes I got {9:37, 9:51}. That's a 7% to 11% speed improvement.
While the povray bench is purely synthetic, it is still nice to see that such a simple change has done quite a decent speed increase.

For testing, persons should run a variety of games to see improvements where one is limited due to CPU emulation, not CPU limited in say the video backend or GPU emulation.
It shouldn't cause any emulation issues, or speed regressions. But of course it should always be tested for.
This only affects the Jit64 and JitArm32 CPU cores. It doesn't touch the Jit64IL or JitArmIL CPU cores.
Doesn't matter in most cases for Android since in 90% of cases we are limited by the video drivers on Mali and Adreno devices. Currently our WIP system isn't outputting APK files that anyone can download, so we'll have to wait on that.

(04-30-2014, 11:19 PM)haddockd Wrote: With the new Zelda uCode HLE change committed, I do not have any games that seem CPU limited (or at least I dont see any slowdowns). Would turning frame limiter off and testing that way be valid?

I had issues with our WIP build system since this is the first time I used it, the previous builds didn't have any of the changes in it.

JMC's tests are still valid since he compiled his own.

Thanks
I'm seeing a pretty good improvement in Metroid Prime, when compared to the same revision without these changes. Though I can't exactly measure it, because it's jumping around all the time, it maxes out at around 220FPS without the changes, and 236FPS with them.