diff options
| author | Vladimir Marko <vmarko@google.com> | 2018-03-26 16:04:48 +0100 |
|---|---|---|
| committer | Vladimir Marko <vmarko@google.com> | 2018-03-27 12:24:23 +0100 |
| commit | e37dc6ee0489565f911aeb792d627d942a3ae4cd (patch) | |
| tree | 78d9c75ddeff8876616e8bc1a9ba0ae6594672a2 /compiler/optimizing/codegen_test_utils.h | |
| parent | fe94875d94ef8c06f6322021d501d58bd64c1606 (diff) | |
Fix 036-finalizer for JIT-at-first-use gcstress.
The array allocation in the OptimizingCompiler::JitCompile()
can trigger a GC, so calling a method and holding only onto
a WeakReference<> may actually cause the referred object to
be collected. Work around this in the 036-finalizer test by
avoiding the method call when we expect that object to stay
alive.
Strangely, the Heap::CheckGcStressMode() causes the GC for
x86-64 but not for x86 in this test based on the backtrace
comparisons. So the 32-bit test was actually passing.
Test: testrunner.py --host -t 036-finalizer \
--jit --runtime-option=-Xjitthreshold=0
Bug: 62611253
Bug: 76454261
Change-Id: I10eb73beec18c66e4f7f1d125aa9e5db340a9d49
Diffstat (limited to 'compiler/optimizing/codegen_test_utils.h')
0 files changed, 0 insertions, 0 deletions