Permalink
Browse files

JitInterface: Move explanatory comment of ClearSafe() to the function…

…'s prototype

Puts the comment in the header where it's more likely to be seen
initially. We can also remove the TODO, given doing nothing or returning
an error is what is generally done for the JIT interface if the JIT
instance isn't valid.
  • Loading branch information...
lioncash committed Aug 27, 2018
1 parent 307d5d5 commit d40022d6d07dfd93569c8d993b92b901fbde115b
Showing with 3 additions and 4 deletions.
  1. +0 −4 Source/Core/Core/PowerPC/JitInterface.cpp
  2. +3 −0 Source/Core/Core/PowerPC/JitInterface.h
@@ -211,10 +211,6 @@ void ClearCache()
}
void ClearSafe()
{
// This clear is "safe" in the sense that it's okay to run from
// inside a JIT'ed block: it clears the instruction cache, but not
// the JIT'ed code.
// TODO: There's probably a better way to handle this situation.
if (g_jit)
g_jit->GetBlockCache()->Clear();
}
@@ -55,6 +55,9 @@ bool HandleStackFault();
// Clearing CodeCache
void ClearCache();
// This clear is "safe" in the sense that it's okay to run from
// inside a JIT'ed block: it clears the instruction cache, but not
// the JIT'ed code.
void ClearSafe();
// If "forced" is true, a recompile is being requested on code that hasn't been modified.

0 comments on commit d40022d

Please sign in to comment.