diff options
author | 2024-03-22 10:47:58 +0000 | |
---|---|---|
committer | 2024-03-25 15:13:59 +0000 | |
commit | b71150621fd1357e4be1bf2644a3fd99e69bc933 (patch) | |
tree | 56245d40e59089c748fadab509d93ddf860c6fc5 /libartbase/base/bit_vector.cc | |
parent | 00fbc4047bd6a1984c333b93fc39e73e61a2521a (diff) |
Rename MallocAllocator to CallocAllocator
It was a misnomer since MallocAllocator was internally calling
calloc. The difference is that calloc sets the memory to zero
which malloc does not.
Bug: 329037671
Test: art/test/testrunner/testrunner.py --host --64 --optimizing -b
Change-Id: I77f44df2681b64a25e1d06773b2a2ed150748e00
Diffstat (limited to 'libartbase/base/bit_vector.cc')
-rw-r--r-- | libartbase/base/bit_vector.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/libartbase/base/bit_vector.cc b/libartbase/base/bit_vector.cc index 85f326385e..5b022b11c2 100644 --- a/libartbase/base/bit_vector.cc +++ b/libartbase/base/bit_vector.cc @@ -51,7 +51,6 @@ BitVector::BitVector(uint32_t start_bits, // * `ScopedArenaAllocator` which does not. // We also have `NoopAllocator` but that allocator should never call this method (as the Alloc // call will turn into a LOG(FATAL)). - // As a note, MallocAllocator is a misnomer as it uses `calloc` which sets the memory to zero. ClearAllBits(); } |