diff options
| author | Calin Juravle <calin@google.com> | 2017-05-23 14:24:55 -0700 |
|---|---|---|
| committer | Calin Juravle <calin@google.com> | 2017-05-25 22:14:27 +0000 |
| commit | 1e8ba3736198056d034dda149903baa5974a5fa5 (patch) | |
| tree | 9155e8f3393a637468ccd8e945a5a660ff0995c8 /test/ProfileTestMultiDex/Main.java | |
| parent | 60889dcb3fe8e718debaddd6d2fb05a880ed87fa (diff) | |
Do not deopt when using AOT inline caches
Generating a deopt does not ensure that we will actually capture the new
types; and the danger is that we could be stuck in a loop with "forever"
deoptimizations. For example, if the method never becomes hot again, the
inline cache will not be updated and the AOT code will keep
deoptimizing.
This is a compromise because we will most likely never update the inline
cache (unless there's another reason to deopt). So we might be stuck
with a sub-optimal inline cache. As a TODO, we could be smarter when
capturing inline caches to mitigate this. (e.g. by having different
thresholds for new and old methods).
Delete test 644 which was testing a regression involving deopts which is
no longer applicable.
Bug: 38412648
Test: m test-art-host
(cherry picked from commit af44e6c5ca0169bc19c6263288a7d889b37db549)
Merged-In: Ib57f9c35ddbc95646aa352ab017e8b59d9466595
Change-Id: I307826bbdc3f994ea12a66243a31f148995f348b
Diffstat (limited to 'test/ProfileTestMultiDex/Main.java')
0 files changed, 0 insertions, 0 deletions