From 6cdabe1f2e760af91d8a23d47e4bbf06d0120bd4 Mon Sep 17 00:00:00 2001 From: Santiago Aboy Solanes Date: Fri, 18 Feb 2022 15:27:43 +0000 Subject: Update runtime/ implications to use (D)CHECK_IMPLIES Follow-up to aosp/1988868 in which we added the (D)CHECK_IMPLIES macro. This CL uses it on compiler/ occurrences found by a regex. Test: art/test/testrunner/testrunner.py --host --64 --optimizing -b Change-Id: Id4ee45b41bad85a1f0d98c1e88af6baa3e34a662 --- runtime/interpreter/interpreter.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'runtime/interpreter/interpreter.cc') diff --git a/runtime/interpreter/interpreter.cc b/runtime/interpreter/interpreter.cc index b60a384ca5..38c94abf06 100644 --- a/runtime/interpreter/interpreter.cc +++ b/runtime/interpreter/interpreter.cc @@ -328,7 +328,7 @@ static inline JValue Execute( // Lock counting is a special version of accessibility checks, and for simplicity and // reduction of template parameters, we gate it behind access-checks mode. - DCHECK(!method->SkipAccessChecks() || !method->MustCountLocks()); + DCHECK_IMPLIES(method->SkipAccessChecks(), !method->MustCountLocks()); VLOG(interpreter) << "Interpreting " << method->PrettyMethod(); -- cgit v1.2.3-59-g8ed1b