DSPAnalyzer: Hide implementation details

Makes accessing flags a part of the function interface instead of exposing
an internal variable.
This commit is contained in:
Lioncash committed 2016-12-26 21:18:18 -05:00
1 parent cd29d565c4
commit a8459fc189
5 files changed
+35 -30

No files matched your search

@@ -100,7 +100,7 @@ void Step()
u16 opc = dsp_fetch_code();
ExecuteInstruction(UDSPInstruction(opc));
if (DSPAnalyzer::code_flags[static_cast<u16>(g_dsp.pc - 1u)] & DSPAnalyzer::CODE_LOOP_END)
if (DSPAnalyzer::GetCodeFlags(static_cast<u16>(g_dsp.pc - 1u)) & DSPAnalyzer::CODE_LOOP_END)
HandleLoop();
}
@@ -158,7 +158,7 @@ int RunCyclesDebug(int cycles)
return cycles;
}
// Idle skipping.
if (DSPAnalyzer::code_flags[g_dsp.pc] & DSPAnalyzer::CODE_IDLE_SKIP)
if (DSPAnalyzer::GetCodeFlags(g_dsp.pc) & DSPAnalyzer::CODE_IDLE_SKIP)
return 0;
Step();
cycles--;
@@ -208,7 +208,7 @@ int RunCycles(int cycles)
if (g_dsp.cr & CR_HALT)
return 0;
// Idle skipping.
if (DSPAnalyzer::code_flags[g_dsp.pc] & DSPAnalyzer::CODE_IDLE_SKIP)
if (DSPAnalyzer::GetCodeFlags(g_dsp.pc) & DSPAnalyzer::CODE_IDLE_SKIP)
return 0;
Step();
cycles--;