Mitigate performance impact of respecting FP bit #136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #135 we switched from a static
OpcodeGrabber
table to acurOpcodeGrabber
pointer inppc_main_opcode
. This results in an extra indirection (as far as generated assembly having an additional load), which reduces execution speed.Switch to making the opcode grabber into a parameter to
ppc_main_opcode
, and makeppc_exec_inner
keep it up to date (via anEXEF_OPCODE
exception flag).Also fixes FPU instructions in
ppctests
- we now need to set the FP MSR bit when initializing the CPU.