• Austin Clements's avatar
    runtime: perform publication barrier even for noscan objects · d8b08c3a
    Austin Clements authored
    Currently we only execute a publication barrier for scan objects (and
    skip it for noscan objects). This used to be okay because GC would
    never consult the object itself (so it wouldn't observe uninitialized
    memory even if it found a pointer to a noscan object), and the heap
    bitmap was pre-initialized to noscan.
    
    However, now we explicitly initialize the heap bitmap for noscan
    objects when we allocate them. While the GC will still never consult
    the contents of a noscan object, it does need to see the initialized
    heap bitmap. Hence, we need to execute a publication barrier to make
    the bitmap visible before user code can expose a pointer to the newly
    allocated object even for noscan objects.
    
    Change-Id: Ie4133c638db0d9055b4f7a8061a634d970627153
    Reviewed-on: https://go-review.googlesource.com/23043
    Run-TryBot: Austin Clements <austin@google.com>
    TryBot-Result: Gobot Gobot <gobot@golang.org>
    Reviewed-by: 's avatarRick Hudson <rlh@golang.org>
    d8b08c3a
Name
Last commit
Last update
.github Loading commit data...
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...