From 23fbcecf131f025bf1258eddfc594f528ff9c297 Mon Sep 17 00:00:00 2001 From: Fiora Date: Thu, 25 Sep 2014 07:03:58 -0700 Subject: [PATCH] JIT: enable block linking and idle skipping in debug mode They can still be turned off, just don't force them off. Also remove some dated comments. --- Source/Core/Core/PowerPC/Jit64/Jit.cpp | 22 ++++------------------ 1 file changed, 4 insertions(+), 18 deletions(-) diff --git a/Source/Core/Core/PowerPC/Jit64/Jit.cpp b/Source/Core/Core/PowerPC/Jit64/Jit.cpp index 9b88538935..775904c431 100644 --- a/Source/Core/Core/PowerPC/Jit64/Jit.cpp +++ b/Source/Core/Core/PowerPC/Jit64/Jit.cpp @@ -174,26 +174,12 @@ bool Jit64::HandleFault(uintptr_t access_address, SContext* ctx) void Jit64::Init() { jo.optimizeStack = true; - /* This will enable block linking in JitBlockCache::FinalizeBlock(), it gives faster execution but may not - be as stable as the alternative (to not link the blocks). However, I have not heard about any good examples - where this cause problems, so I'm enabling this by default, since I seem to get perhaps as much as 20% more - fps with this option enabled. If you suspect that this option cause problems you can also disable it from the - debugging window. */ - if (SConfig::GetInstance().m_LocalCoreStartupParameter.bEnableDebugging) + jo.enableBlocklink = true; + if (!SConfig::GetInstance().m_LocalCoreStartupParameter.bJITBlockLinking || + SConfig::GetInstance().m_LocalCoreStartupParameter.bMMU) { + // TODO: support block linking with MMU jo.enableBlocklink = false; - SConfig::GetInstance().m_LocalCoreStartupParameter.bSkipIdle = false; - } - else - { - if (!SConfig::GetInstance().m_LocalCoreStartupParameter.bJITBlockLinking) - { - jo.enableBlocklink = false; - } - else - { - jo.enableBlocklink = !SConfig::GetInstance().m_LocalCoreStartupParameter.bMMU; - } } jo.fpAccurateFcmp = SConfig::GetInstance().m_LocalCoreStartupParameter.bEnableFPRF; jo.optimizeGatherPipe = true;