From 0984e483c1b8033250a32b11f112ae3e65eef39b Mon Sep 17 00:00:00 2001 From: Vladimir Marko Date: Wed, 27 Mar 2019 16:41:41 +0000 Subject: Style cleanup for ObjPtr<>-ify changes. Replace "ObjPtr<.> const" with "const ObjPtr<.>". Test: m test-art-host-gtest Test: testrunner.py --host --optimizing Bug: 31113334 Change-Id: I5a1c080bc88b091e15ee9eb0bb1ef6f6f290701c --- runtime/gc/reference_processor.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'runtime/gc/reference_processor.cc') diff --git a/runtime/gc/reference_processor.cc b/runtime/gc/reference_processor.cc index 49446399fd..b0fc7a6ae4 100644 --- a/runtime/gc/reference_processor.cc +++ b/runtime/gc/reference_processor.cc @@ -91,7 +91,7 @@ ObjPtr ReferenceProcessor::GetReferent(Thread* self, // Under read barrier / concurrent copying collector, it's not safe to call GetReferent() when // weak ref access is disabled as the call includes a read barrier which may push a ref onto the // mark stack and interfere with termination of marking. - ObjPtr const referent = reference->GetReferent(); + const ObjPtr referent = reference->GetReferent(); // If the referent is null then it is already cleared, we can just return null since there is no // scenario where it becomes non-null during the reference processing phase. if (UNLIKELY(!SlowPathEnabled()) || referent == nullptr) { -- cgit v1.2.3-59-g8ed1b