From f79077ad9e7b1e5b885466dce7f672130ee7efea Mon Sep 17 00:00:00 2001 From: Vladimir Marko Date: Thu, 23 Jan 2025 14:45:35 +0000 Subject: Optimizing: Rename `HCodeFlowSimplifier`... ... to `HControlFlowSimplifier` because "control flow" is the correct technical term. Test: m test-art-host-gtest Test: testrunner.py --host --optimizing Change-Id: I2607ac699fa33c3e7ca7f54364e1e8497148412b --- compiler/optimizing/dead_code_elimination.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'compiler/optimizing/dead_code_elimination.cc') diff --git a/compiler/optimizing/dead_code_elimination.cc b/compiler/optimizing/dead_code_elimination.cc index ede909526d..c5ec0b93b2 100644 --- a/compiler/optimizing/dead_code_elimination.cc +++ b/compiler/optimizing/dead_code_elimination.cc @@ -526,10 +526,10 @@ void HDeadCodeElimination::MaybeAddPhi(HBasicBlock* block) { // | // 8 // `7` (which would be `block` in this example), and `6` will come from both the true path and - // the false path of `1`. We bumped into something similar in `HCodeFlowSimplifier`. See - // `HCodeFlowSimplifier::TryFixupDoubleDiamondPattern()`. + // the false path of `1`. We bumped into something similar in `HControlFlowSimplifier`. See + // `HControlFlowSimplifier::TryFixupDoubleDiamondPattern()`. // TODO(solanes): Figure out if we can fix up the graph into a double diamond in a generic way - // so that `HDeadCodeElimination` and `HCodeFlowSimplifier` can take advantage of it. + // so that `HDeadCodeElimination` and `HControlFlowSimplifier` can take advantage of it. if (!same_input) { // `1` and `7` having the opposite condition is a case we are missing. We could potentially -- cgit v1.2.3-59-g8ed1b