summaryrefslogtreecommitdiff
path: root/runtime/class_linker.cc
diff options
context:
space:
mode:
author Vladimir Marko <vmarko@google.com> 2024-10-04 16:14:16 +0200
committer VladimĂ­r Marko <vmarko@google.com> 2024-10-07 12:01:13 +0000
commitf758d6a7530324ca95a69d551ce48f9a0cc9014c (patch)
tree8391a29d8303ac032263b0c8b9af4e09d2e28922 /runtime/class_linker.cc
parentd576392c76d75335d8284217f2153bdace62b355 (diff)
Fix `VerificationResults` use in `OatWriter`.
Since https://android-review.googlesource.com/2236075 the `OatWriter` has been using a null `VerificationResults` because `CreateOatWriters()` is called before initializing the `verification_results_` in `Dex2Oat`. As the `OatWriter` is using it only to select between two `ClassStatus` values that currently lead to the very same behavior in the `ClassLinker::VerifyClassUsingOatFile()` (but with different comments and therefore prone to diverging), this did not yet lead to any observable difference in behavior. Test: m test-art-host-gtest Test: testrunner.py --host --optimizing. Change-Id: I3f0b67497358ac98b4980691f80044a5b0f0fc17
Diffstat (limited to 'runtime/class_linker.cc')
-rw-r--r--runtime/class_linker.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/class_linker.cc b/runtime/class_linker.cc
index cad968dfc2..b23a543b5d 100644
--- a/runtime/class_linker.cc
+++ b/runtime/class_linker.cc
@@ -5165,7 +5165,7 @@ bool ClassLinker::VerifyClassUsingOatFile(Thread* self,
return true;
}
if (oat_file_class_status >= ClassStatus::kVerifiedNeedsAccessChecks) {
- // We return that the clas has already been verified, and the caller should
+ // We return that the class has already been verified, and the caller should
// check the class status to ensure we run with access checks.
return true;
}