I cannot reproduce this with go1.5.1:

C:\dev\src\t>go version
go version go1.5.1 windows/amd64

C:\dev\src\t>go env
set GOARCH=386
set GOBIN=
set GOEXE=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=linux
set GOPATH=c:\dev
set GORACE=
set GOROOT=c:\dev\go
set GOTOOLDIR=c:\dev\go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=
set CC=gcc
set GOGCCFLAGS=-fPIC -m32 -fmessage-length=0
set CXX=g++
set CGO_ENABLED=0

C:\dev\src\t>type main.go
package main

import (
    "fmt"
)

func main() {
    fmt.Println("hello go")
}
C:\dev\src\t>go build

C:\dev\src\t>

I can successfully build the exe. I can even run it on linux.

Reopen if you can provide more steps to try. Thank you.

Alex

@alexbrainman I re-ran the experiment on two machines and kept everything exactly the same as you have documented. Here are my findings:

• Windows 8.1 Pro (i5) -> build is successful and I can run the executable on Linux.
• Windows 10 Home (i7) -> build fails with the error in my original post.

I don't know. I don't have Windows 10 computers. Perhaps this bug is tickled by that.

Alex

I'm still working on isolating the issue. I was NOT able to reproduce the issue on Windows 10 Pro (i5) running in VirtualBox.

I'm closing this issue after all. How the issue went away for me is a mystery to me, but for the record here is what I did on my machine following successful tests on other machines:

1.) Reinstall Go for Windows amd64
Test Result: build failed
2.) Uninstall Go and use ZIP version for Windows amd64
Test Result: build passed
3.) Reinstall Go for Windows amd64
Test Result: build passed

Please reopen this issue.

I see a similar issue when cross compiling to GOOS=linux on macosx using go 1.5.1 It happens in the link step, AFAICT from using the -v option to go build.

runtime.cgocallbackg: nosplit stack overflow
504 assumed on entry to runtime.cgocallbackg (nosplit)
416 after runtime.cgocallbackg (nosplit) uses 88
408 on entry to runtime.exitsyscall (nosplit)
288 after runtime.exitsyscall (nosplit) uses 120
280 on entry to runtime.exitsyscallfast (nosplit)
120 after runtime.exitsyscallfast (nosplit) uses 160
112 on entry to runtime.writebarrierptr (nosplit)
64 after runtime.writebarrierptr (nosplit) uses 48
56 on entry to runtime.writebarrierptr_nostore1 (nosplit)
0 after runtime.writebarrierptr_nostore1 (nosplit) uses 56
-8 on entry to runtime.acquirem (nosplit)
reflect.typelinks: nosplit stack overflow
504 assumed on entry to reflect.typelinks (nosplit)
352 after reflect.typelinks (nosplit) uses 152
344 on entry to runtime.typedmemmove (nosplit)
320 after runtime.typedmemmove (nosplit) uses 24
312 on entry to runtime.heapBitsBulkBarrier (nosplit)
192 after runtime.heapBitsBulkBarrier (nosplit) uses 120
184 on entry to runtime.throw (nosplit)
160 after runtime.throw (nosplit) uses 24
152 on entry to runtime.dopanic (nosplit)
72 after runtime.dopanic (nosplit) uses 80
64 on entry to runtime.getcallerpc (nosplit)
56 after runtime.getcallerpc (nosplit) uses 8
48 on entry to runtime.nextBarrierPC (nosplit)
8 after runtime.nextBarrierPC (nosplit) uses 40
0 on entry to runtime.panicindex
-8 on entry to runtime.morestack (nosplit)
runtime.cgocallback_gofunc: nosplit stack overflow
504 assumed on entry to runtime.cgocallback_gofunc (nosplit)
496 after runtime.cgocallback_gofunc (nosplit) uses 8
488 on entry to runtime.cgocallbackg (nosplit)
400 after runtime.cgocallbackg (nosplit) uses 88
392 on entry to runtime.exitsyscall (nosplit)
272 after runtime.exitsyscall (nosplit) uses 120
264 on entry to runtime.exitsyscallfast (nosplit)
104 after runtime.exitsyscallfast (nosplit) uses 160
96 on entry to runtime.writebarrierptr (nosplit)
48 after runtime.writebarrierptr (nosplit) uses 48
40 on entry to runtime.writebarrierptr_nostore1 (nosplit)
-16 after runtime.writebarrierptr_nostore1 (nosplit) uses 56

The reflect.typelinks issue is fixed on tip by https://golang.org/cl/16932.

@rrh: are you compiling with -N? The stack sizes you are reporting are too large. The values I see are

cgocallbackg 88
exitsyscall 32
exitsyscallfast 88
writebarrierptr 40
writebarrierptr_nostore1 48

I was using the -N flag. If I don't use it, the problem goes away.

I'm getting the same error on Windows 10(i7).
If go1.5.1.windows-amd64 from zip used - build succesfully passed, but resulting exe with simple "Hello world" stucking and not running.
If use "-a" flag or remove windows_amd64 folder from "go\pkg" folder - build with "-N -l" failed. Without "-N" passed but resulting exe stucks and not running.

@Agnikay In general it doesn't help much to comment on a closed issue. Few people will see your comment. In this case, see #13431 .