[oilpan,wtf] Rework HashTable write barriers
Instead of emitting write barriers for single writes in HashTable, conservatively emit a barrier for the backing store during rehashing. This moves us in the tradeoff space: - Removes 40KiB of binary bloat - Avoids emitting barriers when re-inserting single elements which improves throughput for the case where incremental marking is off - Emits a single conservative barrier at the end of RehashTo. This potentially means that we (re-)scan more objects when incremental marking is on Bug: chromium:839514, chromium:757440 Change-Id: Ib5495c9e2210836424d7b26f2138d852f8dafec7 Reviewed-on: https://chromium-review.googlesource.com/1055400 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#558713}
Showing
Please register or sign in to comment