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.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'compiler/optimizing/scheduler.cc') diff --git a/compiler/optimizing/scheduler.cc b/compiler/optimizing/scheduler.cc index cb340f530b..8f18ccff5f 100644 --- a/compiler/optimizing/scheduler.cc +++ b/compiler/optimizing/scheduler.cc @@ -316,7 +316,7 @@ void SchedulingGraph::AddDependencies(SchedulingNode* instruction_node, } // Scheduling barrier dependencies. - DCHECK(!is_scheduling_barrier || contains_scheduling_barrier_); + DCHECK_IMPLIES(is_scheduling_barrier, contains_scheduling_barrier_); if (contains_scheduling_barrier_) { // A barrier depends on instructions after it. And instructions before the // barrier depend on it. -- cgit v1.2.3-59-g8ed1b