Fix a couple of places to check for instrumented entry points
There are a couple of places where we missed the check for instrumented
entry points:
- In resoultion stubs, when we get the code to execute we need to check
if we need an instrumentation entry point. Resolution stubs could
suspend so it is possible that we instrumented after resolution stub
started executing.
- When undeoptimizing a method, though the method itself is
undeoptimized we may still need instrumentation entry points.
Instrumentation entry points are also required to deoptimize the
caller.
Bug: 222479430
Test: art/test.py
Change-Id: Id520b5f6ff47fddee67e2bf8d3396d6d9db7fff6
3 files changed