From 56dcaeec46dd53e271d6f201d2028996bf19f9dd Mon Sep 17 00:00:00 2001
From: Santiago Aboy Solanes <solanes@google.com>
Date: Fri, 22 Mar 2024 10:45:15 +0000
Subject: Remove extra uses of ClearAllBits

ArenaBitVector creation guarantees it starts empty. Add a debug
check to make sure this assumption doesn't change.

Note that ArenaAllocator guarantees zero-initialized memory but
ScopedArenaAllocators do not. This is fine either way since the
BitVector constructor calls ClearAllBits.

Bug: 329037671
Test: art/test/testrunner/testrunner.py --host --64 --optimizing -b
Change-Id: Icbf5e5dd1869e80b5d5828ecca9f13de30c0242b
---
 compiler/optimizing/ssa_phi_elimination.cc | 1 -
 1 file changed, 1 deletion(-)

(limited to 'compiler/optimizing/ssa_phi_elimination.cc')

diff --git a/compiler/optimizing/ssa_phi_elimination.cc b/compiler/optimizing/ssa_phi_elimination.cc
index 1d9be3956a..0796acc687 100644
--- a/compiler/optimizing/ssa_phi_elimination.cc
+++ b/compiler/optimizing/ssa_phi_elimination.cc
@@ -143,7 +143,6 @@ bool SsaRedundantPhiElimination::Run() {
                                        graph_->GetCurrentInstructionId(),
                                        /* expandable= */ false,
                                        kArenaAllocSsaPhiElimination);
-  visited_phis_in_cycle.ClearAllBits();
   ScopedArenaVector<HPhi*> cycle_worklist(allocator.Adapter(kArenaAllocSsaPhiElimination));
 
   while (!worklist.empty()) {
-- 
cgit v1.2.3-59-g8ed1b