diff options
author | 2024-09-30 09:04:41 +0000 | |
---|---|---|
committer | 2024-09-30 13:19:59 +0000 | |
commit | e159a3bce2dc2dda37127592e8f0b39c377e05ec (patch) | |
tree | 0781d0f7353358aa98b5e609228e3665987a43c1 /libartbase/base/bit_vector.h | |
parent | 7b74ddc161107c60ab405e8ec3794d3aa32df5dc (diff) |
Revert^5 "Object.clone() allocates more movable objects"
This reverts commit ea269f69d05fe333e4b36634b925c3c40fc8ce95.
Bug: 355291033
Bug: 354087169
Bug: 360363656
Bug: 361327909
Bug: 364629185
Reason for revert: Failure on asan:
+addressOf succeeded on movable object
+Unexpectedly got 0 address in checkMovable
Change-Id: I1f27845bf3fb7a1542f24b943d999f2d4da5e23a
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: |