tree d96564388c2eea266fa5feb307b90ddecd4e460d
parent c4adba240f9d5af8ab0534316d6b05bd988c432c
author Ian Lance Taylor <iant@golang.org> 1498195569 -0700
committer Ian Lance Taylor <iant@golang.org> 1498233792 +0000

compiler: add go:notinheap magic comment

Implement go:notinheap as the gc compiler does. A type marked as
go:notinheap may not live in the heap, and does not require a write
barrier. Struct and array types that incorporate notinheap types are
themselves notinheap. Allocating a value of a notinheap type on the
heap is an error.

This is not just an optimization. There is code where a write barrier
may not occur that was getting a write barrier with gccgo but not gc,
because the types in question were notinheap. The case I found was
setting the mcache field in exitsyscallfast.

Change-Id: If7c441b8066f6c110aab5207b2ba756d360c9d50
Reviewed-on: https://go-review.googlesource.com/46490
Reviewed-by: Than McIntosh <thanm@google.com>