From f6d1e0f6196cb3669dfb4eed8ceef679b0588c0f Mon Sep 17 00:00:00 2001 From: Vladimir Marko Date: Mon, 23 May 2016 15:32:42 +0100 Subject: Compile JNI stubs for verify-profile and interpret-only. This is the intended behavior to have a good JNI transition performance. Bug: 28902384 (cherry picked from commit 8c185bf0c6f18a5349bc87a7e3751ba06d90f461) Change-Id: I52767909b916ada3c619206c8838b85bff5ac316 --- compiler/driver/compiler_driver.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'compiler/driver/compiler_driver.cc') diff --git a/compiler/driver/compiler_driver.cc b/compiler/driver/compiler_driver.cc index 1ab1d31f09..d20f51001c 100644 --- a/compiler/driver/compiler_driver.cc +++ b/compiler/driver/compiler_driver.cc @@ -553,8 +553,8 @@ static void CompileMethod(Thread* self, MethodReference method_ref(&dex_file, method_idx); if ((access_flags & kAccNative) != 0) { - // Are we interpreting only and have support for generic JNI down calls? - if (!driver->GetCompilerOptions().IsCompilationEnabled() && + // Are we extracting only and have support for generic JNI down calls? + if (!driver->GetCompilerOptions().IsJniCompilationEnabled() && InstructionSetHasGenericJniStub(driver->GetInstructionSet())) { // Leaving this empty will trigger the generic JNI version } else { -- cgit v1.2.3-59-g8ed1b