• Rick Hudson's avatar
    runtime: Adjust when write barriers are active · d0eab030
    Rick Hudson authored
    Even though the world is stopped the GC may do pointer
    writes that need to be protected by write barriers.
    This means that the write barrier must be on
    continuously from the time the mark phase starts and
    the mark termination phase ends. Checks were added to
    ensure that no allocation happens during a GC.
    
    Hoist the logic that clears pools the start of the GC
    so that the memory can be reclaimed during this GC cycle.
    
    Change-Id: I9d1551ac5db9bac7bac0cb5370d5b2b19a9e6a52
    Reviewed-on: https://go-review.googlesource.com/6990Reviewed-by: 's avatarAustin Clements <austin@google.com>
    d0eab030
Name
Last commit
Last update
api Loading commit data...
doc Loading commit data...
lib/time Loading commit data...
misc Loading commit data...
src Loading commit data...
test Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
AUTHORS Loading commit data...
CONTRIBUTING.md Loading commit data...
CONTRIBUTORS Loading commit data...
LICENSE Loading commit data...
PATENTS Loading commit data...
README.md Loading commit data...
favicon.ico Loading commit data...
robots.txt Loading commit data...