diff options
| author | 2023-09-07 13:42:18 +0000 | |
|---|---|---|
| committer | 2023-09-08 13:13:09 +0000 | |
| commit | 8aa54bd205ae14d523f243bfe6892c65d8e65527 (patch) | |
| tree | 507f38a6dfceb822b5469a54ddbc8f55468f78eb /compiler/optimizing/optimizing_compiler.cc | |
| parent | 9c11f32485128f9eacfd5900bf660d4d29dcf605 (diff) | |
Don't update the compiler filter when using a runtime image.
Before this change, the runtime reports the compiler filter being
"speed-profile" when using a runtime image. This was originally for
reporting the app startup metric under a unique pair of dimension
values (speed-profile, vdex).
However, it turns out that the code that reports the app startup metric
doesn't get the compiler filter from the runtime. Besides, the compiler
filter change can have surprising side-effects. For example, when an app
gets its own optimization status from the Java API
`ApplicationRuntime.getBaseApkOptimizationInfo()`, it may find itself
being in (speed-profile, install) even though its baseline profile is
not used during app install.
Bug: 260557058
Change-Id: I46eb5015f2a382f5363b2bfab15be8c6a86a2f73
Test: Presubmit
Diffstat (limited to 'compiler/optimizing/optimizing_compiler.cc')
0 files changed, 0 insertions, 0 deletions