diff options
author | 2024-08-19 21:32:19 +0000 | |
---|---|---|
committer | 2024-08-19 23:48:03 +0000 | |
commit | 7c89f49c2c542df1a5780fb851e2ef0e0909f48f (patch) | |
tree | 02bc90403e3f56bbb59c7fb1d89b785cd8257b28 /libartbase/base/bit_vector.h | |
parent | 806ace6dfa77cd65b05b20affb6a7e7072dcc845 (diff) |
Revert "Object.clone() allocates more movable objects"
This reverts commit a5001fed23788c966fd87048d7f17ba8c0b51914.
Reason for revert: b/360363656
Change-Id: Ibfea46976bb6434d728c69160edb5904ab7708aa
Diffstat (limited to 'libartbase/base/bit_vector.h')
-rw-r--r-- | libartbase/base/bit_vector.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/libartbase/base/bit_vector.h b/libartbase/base/bit_vector.h index 2eed9702bf..ec94efb09f 100644 --- a/libartbase/base/bit_vector.h +++ b/libartbase/base/bit_vector.h @@ -31,9 +31,9 @@ class ArenaBitVector; /* * Expanding bitmap. Bits are numbered starting from zero. All operations on a BitVector are - * unsynchronized. New BitVectors are not necessarily zeroed out. If the used allocator doesn't - * clear the vector (e.g. ScopedArenaAllocator), the caller is responsible for clearing it (e.g. - * ArenaBitVector). + * unsynchronized. New BitVectors are not necessarily zeroed out. If the used allocator doesn't do + * clear the vector (e.g. ScopedArenaAllocator), the responsibility of clearing it relies on the + * caller (e.g. ArenaBitVector). */ class BitVector { public: |