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/inliner.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'compiler/optimizing/inliner.cc') diff --git a/compiler/optimizing/inliner.cc b/compiler/optimizing/inliner.cc index 88677923b5..1df313d7fc 100644 --- a/compiler/optimizing/inliner.cc +++ b/compiler/optimizing/inliner.cc @@ -961,7 +961,7 @@ bool HInliner::TryInlinePolymorphicCall( // In monomorphic cases when UseOnlyPolymorphicInliningWithNoDeopt() is true, we call // `TryInlinePolymorphicCall` even though we are monomorphic. const bool actually_monomorphic = number_of_types == 1; - DCHECK(!actually_monomorphic || UseOnlyPolymorphicInliningWithNoDeopt()); + DCHECK_IMPLIES(actually_monomorphic, UseOnlyPolymorphicInliningWithNoDeopt()); // We only want to limit recursive polymorphic cases, not monomorphic ones. const bool too_many_polymorphic_recursive_calls = -- cgit v1.2.3-59-g8ed1b