Handle OP_THROW in the method JIT.

The current implementation is to reconstruct the leaf Dalvik frame and
punt to the interpreter, since the amount of work involed to match
each catch block and walk through the stack frames is just not worth
JIT'ing.

Additional changes:
- Fixed a control-flow bug where a block that ends with a throw shouldn't
  have a fall-through block.
- Fixed a code cache lookup bug so that method-based compilation is
  guaranteed a slot in the profiling table.
- Created separate handler routines based on opcode format for the
  method-based JIT.
- Renamed a few core registers that also have special meanings to the
  VM or ARM architecture.

Change-Id: I429b3633f281a0e04d352ae17a1c4f4a41bab156

1 files changed, 1 insertions, 1 deletions

diff --git a/vm/compiler/codegen/arm/FP/ThumbVFP.c b/vm/compiler/codegen/arm/FP/ThumbVFP.c
index bec54ca77..f685f2469 100644
--- a/vm/compiler/codegen/arm/FP/ThumbVFP.c
+++ b/vm/compiler/codegen/arm/FP/ThumbVFP.c
@@ -38,7 +38,7 @@ static void loadValueAddressDirect(CompilationUnit *cUnit, RegLocation rlSrc,
      }
      dvmCompilerClobber(cUnit, rDest);
      dvmCompilerLockTemp(cUnit, rDest);
-     opRegRegImm(cUnit, kOpAdd, rDest, rFP,
+     opRegRegImm(cUnit, kOpAdd, rDest, r5FP,
                  dvmCompilerS2VReg(cUnit, rlSrc.sRegLow) << 2);
 }