diff options
| author | 2017-07-19 23:13:18 -0700 | |
|---|---|---|
| committer | 2017-07-21 09:45:08 -0700 | |
| commit | 64d2d3e9c7d935dfe879f68019970983fee7189d (patch) | |
| tree | 962b71ab236eef1c54080617addc4a44e7686c25 /runtime/monitor_test.cc | |
| parent | 2727d7ca49eea03fc1cd4cf81447e1c2bb7027e7 (diff) | |
ART: Account for OOME during array merging
When joining class types, in the case of arrays it is possible that
a join type cannot be created (e.g., there's no Java heap to actually
create the class). In that case report an unresolved reference. For
AoT this will lead to re-verification at runtime. At runtime, this
will most likely fail the class.
However, have a special cutout that aborts for AoT on the host, to
protect determinism of preopting.
The decision for an unresolved reference type was made as we do not
want to propagate the underlying exception out of verification. This
would require significant work along all call edges, violating the
current design and invariants of the verifier.
Extend reg_type_test.
Bug: 63822536
Test: m test-art-host-gtest-reg_type_test
Change-Id: I823201e3c401b2c2a46a46fad3327a28e049c181
Diffstat (limited to 'runtime/monitor_test.cc')
0 files changed, 0 insertions, 0 deletions