From 3f41a0193eadf037b4003c1996151f386ca07b13 Mon Sep 17 00:00:00 2001
From: Andreas Gampe <agampe@google.com>
Date: Thu, 18 Feb 2016 16:53:41 -0800
Subject: ART: Use optimizing compiler in image_test

Expose some compiler options so we can run the image test with
the optimizing compiler without running into a stack overflow.

Also allow a variable amount of threads in CreateCompilerDriver.
Use 16 as a middle ground on the host to speed up the otherwise
now slowed-down test.

Bug: 27240085
Bug: 27552475
Change-Id: I8db5055d32ae722c8f430903244faa9166cc4886
---
 runtime/common_runtime_test.cc | 1 +
 1 file changed, 1 insertion(+)

(limited to 'runtime/common_runtime_test.cc')

diff --git a/runtime/common_runtime_test.cc b/runtime/common_runtime_test.cc
index 3df9101613..729957f318 100644
--- a/runtime/common_runtime_test.cc
+++ b/runtime/common_runtime_test.cc
@@ -406,6 +406,7 @@ void CommonRuntimeTestImpl::TearDown() {
   int rmdir_cache_result = rmdir(dalvik_cache_.c_str());
   ASSERT_EQ(0, rmdir_cache_result);
   TearDownAndroidData(android_data_, true);
+  dalvik_cache_.clear();
 
   // icu4c has a fixed 10-element array "gCommonICUDataArray".
   // If we run > 10 tests, we fill that array and u_setCommonData fails.
-- 
cgit v1.2.3-59-g8ed1b