AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

[heap] Add missing atomicity parameter in NotifyLeftTrimming.

Browse Source 
Bug: chromium:752461
Change-Id: Ie70a4ed1314e040d0edecece6a1dca7b1fc8d001
Reviewed-on: https://chromium-review.googlesource.com/610083
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#47287}
This commit is contained in:
Ulan Degenbaev 2017-08-10 18:35:09 +02:00 committed by Commit Bot
parent d9b54ff988
commit 17f7efee49
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/heap/incremental-marking.cc
View File

@ -181,8 +181,8 @@ void IncrementalMarking::NotifyLeftTrimming(HeapObject* from, HeapObject* to) {
if (from->address() + kPointerSize == to->address()) {
// The old and the new markbits overlap. The |to| object is either white
// or grey. Set the first bit to make sure that it is grey.
new_mark_bit.Set();
DCHECK(!new_mark_bit.Next().Get());
new_mark_bit.Set<kAtomicity>();
DCHECK(!new_mark_bit.Next().Get<kAtomicity>());
} else {
bool success = Marking::WhiteToGrey<kAtomicity>(new_mark_bit);
DCHECK(success);