Remove hard-coded list of boot image array classes.
This is no longer needed now that array classes in profiles
are properly supported. All these classes are actually in
the current boot image profile and expected to be in future
boot image profiles as long as they shall be needed.
Test: m
Bug: 148067697
Change-Id: I4a94fee756dd8ef05c252f67a58536b5409d3e19
diff --git a/dex2oat/driver/compiler_driver.cc b/dex2oat/driver/compiler_driver.cc
index d17177c..d9509b0 100644
--- a/dex2oat/driver/compiler_driver.cc
+++ b/dex2oat/driver/compiler_driver.cc
@@ -1025,21 +1025,6 @@
return;
}
- // A hard-coded list of array classes that should be in the primary boot image profile. The impact
- // of each class can be approximately measured by comparing oatdump output with and without it:
- // `m dump-oat-boot && grep -cE 'Class.*VisiblyInitialized' boot.host-<arch>.oatdump.txt`.
- // - b/150319075: File[]
- // - b/156098788: int[][], int[][][], short[][], byte[][][]
- //
- // TODO: Implement support for array classes in profiles and remove this workaround. b/148067697
- if (GetCompilerOptions().IsBootImage()) {
- image_classes->insert("[Ljava/io/File;");
- image_classes->insert("[[I");
- image_classes->insert("[[[I");
- image_classes->insert("[[S");
- image_classes->insert("[[[B");
- }
-
TimingLogger::ScopedTiming t("LoadImageClasses", timings);
if (GetCompilerOptions().IsBootImage()) {