Commit afb35081 authored by Euan Kemp's avatar Euan Kemp Committed by Austin Clements

runtime: correct writebarrier typos

Change-Id: I7d67c3d64be915f0be5932d2c068606d74f93c29
Reviewed-on: https://go-review.googlesource.com/34378
Run-TryBot: Austin Clements <austin@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: 's avatarAustin Clements <austin@google.com>
parent d0501f1d
...@@ -510,7 +510,7 @@ func semacreate(mp *m) { ...@@ -510,7 +510,7 @@ func semacreate(mp *m) {
// May run with m.p==nil, so write barriers are not allowed. This // May run with m.p==nil, so write barriers are not allowed. This
// function is called by newosproc0, so it is also required to // function is called by newosproc0, so it is also required to
// operate without stack guards. // operate without stack guards.
//go:nowritebarrierc //go:nowritebarrierrec
//go:nosplit //go:nosplit
func newosproc(mp *m, stk unsafe.Pointer) { func newosproc(mp *m, stk unsafe.Pointer) {
const _STACK_SIZE_PARAM_IS_A_RESERVATION = 0x00010000 const _STACK_SIZE_PARAM_IS_A_RESERVATION = 0x00010000
...@@ -527,7 +527,7 @@ func newosproc(mp *m, stk unsafe.Pointer) { ...@@ -527,7 +527,7 @@ func newosproc(mp *m, stk unsafe.Pointer) {
// Used by the C library build mode. On Linux this function would allocate a // Used by the C library build mode. On Linux this function would allocate a
// stack, but that's not necessary for Windows. No stack guards are present // stack, but that's not necessary for Windows. No stack guards are present
// and the GC has not been initialized, so write barriers will fail. // and the GC has not been initialized, so write barriers will fail.
//go:nowritebarrierc //go:nowritebarrierrec
//go:nosplit //go:nosplit
func newosproc0(mp *m, stk unsafe.Pointer) { func newosproc0(mp *m, stk unsafe.Pointer) {
newosproc(mp, stk) newosproc(mp, stk)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment