From 86d6cd53385eae365f16f45e1a5947cc6595eb63 Mon Sep 17 00:00:00 2001 From: David Srbecky Date: Wed, 2 Dec 2020 18:13:10 +0000 Subject: Remove DexCache arrays from image. Remove the hashtable storage from the image and allocate it at runtime instead (but keep the DexCache object in the image). For compiled code, we have largely moved to using .bss, so the DexCache just costs us unnecessary extra space and dirty pages. For interpreted code, the hashtables are too small and will be overridden many times over at run-time regardless. The next step will be to make DexCache variable-size so it can adapt to both of the extremes (taking minimal amount of memory for compiled code and avoiding cache evictions in interpreter). Test: test.py --host Change-Id: I9f89e8f19829b812cf85dea1a964259ed8b87f4d --- compiler/optimizing/builder.cc | 1 - 1 file changed, 1 deletion(-) (limited to 'compiler/optimizing/builder.cc') diff --git a/compiler/optimizing/builder.cc b/compiler/optimizing/builder.cc index 33dbf4e45e..decc4a815a 100644 --- a/compiler/optimizing/builder.cc +++ b/compiler/optimizing/builder.cc @@ -33,7 +33,6 @@ #include "optimizing_compiler_stats.h" #include "ssa_builder.h" #include "thread.h" -#include "utils/dex_cache_arrays_layout-inl.h" namespace art { -- cgit v1.2.3-59-g8ed1b