From 56dcaeec46dd53e271d6f201d2028996bf19f9dd Mon Sep 17 00:00:00 2001 From: Santiago Aboy Solanes 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/register_allocator.cc | 1 - 1 file changed, 1 deletion(-) (limited to 'compiler/optimizing/register_allocator.cc') diff --git a/compiler/optimizing/register_allocator.cc b/compiler/optimizing/register_allocator.cc index 54a80555dc..1b3a9a6285 100644 --- a/compiler/optimizing/register_allocator.cc +++ b/compiler/optimizing/register_allocator.cc @@ -214,7 +214,6 @@ bool RegisterAllocator::ValidateIntervals(ArrayRef interval for (size_t i = 0; i < number_of_registers + number_of_spill_slots; ++i) { liveness_of_values.push_back( ArenaBitVector::Create(&allocator, max_end, false, kArenaAllocRegisterAllocatorValidate)); - liveness_of_values.back()->ClearAllBits(); } for (LiveInterval* start_interval : intervals) { -- cgit v1.2.3-59-g8ed1b