From 872ec72de447b2803894e17253399a54a4c10e1f Mon Sep 17 00:00:00 2001 From: Santiago Aboy Solanes Date: Fri, 18 Feb 2022 14:10:25 +0000 Subject: Update compiler/ 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: If63aed969bfb8b31d6fbbcb3bca2b04314c894b7 --- compiler/optimizing/scheduler_arm.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'compiler/optimizing/scheduler_arm.cc') diff --git a/compiler/optimizing/scheduler_arm.cc b/compiler/optimizing/scheduler_arm.cc index f9004d867b..965e1bd9f4 100644 --- a/compiler/optimizing/scheduler_arm.cc +++ b/compiler/optimizing/scheduler_arm.cc @@ -1050,8 +1050,8 @@ void SchedulingLatencyVisitorARM::VisitStaticFieldSet(HStaticFieldSet* instructi void SchedulingLatencyVisitorARM::VisitSuspendCheck(HSuspendCheck* instruction) { HBasicBlock* block = instruction->GetBlock(); - DCHECK((block->GetLoopInformation() != nullptr) || - (block->IsEntryBlock() && instruction->GetNext()->IsGoto())); + DCHECK_IMPLIES(block->GetLoopInformation() == nullptr, + block->IsEntryBlock() && instruction->GetNext()->IsGoto()); // Users do not use any data results. last_visited_latency_ = 0; } -- cgit v1.2.3-59-g8ed1b