heap: Don't call write barrier on vector reallocations
This CL reorders reallocation scenario as follows: 1) allocating a new buffer; 2) moving elements in the current buffer to the new one ***without tracing them or executing write barriers on them*** 3) resetting HeapVector's pointer to the new buffer; 4) executing write barrier on the new buffer. The followup to the CL will be introducing the same optimization for HashTable. Bug: 1021889 Change-Id: I367165ba26045d3a4ca967c7f9f006ff88be4ed4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899883 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#714926}
Showing
This diff is collapsed.
Please register or sign in to comment