diff options
| author | 2021-09-28 15:27:55 +0100 | |
|---|---|---|
| committer | 2021-10-11 07:22:31 +0000 | |
| commit | b0cc5923bf0b0315fa181542c765bfa8b8083cad (patch) | |
| tree | e603f603debced1bdff10f3aed90d8d33456fe20 /compiler/utils/jni_macro_assembler.h | |
| parent | 73c4f79b14492a930903f15553969a4e7ecbefed (diff) | |
With mainline, classes in the boot classpath that hard fail can happen.
Spotted while reviewing code on verifier.
This is to not abort the runtime for a scenario like:
New code in T, not executed in S (but still shipping on S through a
mainline update), relies on the fact a class that was present in S
moved from 'final' to 'non-final'. When verifying on S, this could
lead to hard failures. But given the class is not supposed to execute,
that's OK.
Test: device booting
Change-Id: I68512858e9085dd45c4f9b77ac3f9dea788d3fa4
Diffstat (limited to 'compiler/utils/jni_macro_assembler.h')
0 files changed, 0 insertions, 0 deletions