CPU Backends: Make each CPU backend responsible for initializing its own
instruction tables Previously, all of the internals that handled how the instruction tables are initialized were exposed externally. However, this can all be made private to each CPU backend. If each backend has an Init() function, then this is where the instruction tables should be initialized, it shouldn't be the responsibility of external code to ensure internal validity. This allows for getting rid of all the table initialization shenanigans within JitInterface and PPCTables.
This commit is contained in:
1 parent
5da7d700ca
commit
1ce1304d0f
23 files changed
+44
-171
No files matched your search
@@ -15,7 +15,6 @@
|
||||
#include "Common/StringUtil.h"
|
||||
|
||||
#include "Core/PowerPC/Interpreter/Interpreter.h"
|
||||
#include "Core/PowerPC/Interpreter/Interpreter_Tables.h"
|
||||
#include "Core/PowerPC/JitInterface.h"
|
||||
#include "Core/PowerPC/PowerPC.h"
|
||||
|
||||
@@ -110,15 +109,6 @@ bool UsesFPU(UGeckoInstruction inst)
|
||||
return (info->flags & FL_USE_FPU) != 0;
|
||||
}
|
||||
|
||||
void InitTables(int cpu_core)
|
||||
{
|
||||
// Interpreter ALWAYS needs to be initialized
|
||||
InterpreterTables::InitTables();
|
||||
|
||||
if (cpu_core != PowerPC::CORE_INTERPRETER)
|
||||
JitInterface::InitTables(cpu_core);
|
||||
}
|
||||
|
||||
#define OPLOG
|
||||
#define OP_TO_LOG "mtfsb0x"
|
||||
|
||||
|
||||
Reference in new issue
Block a user