SIGILL: illegal instruction on any go tool under macOS

[carlca]

What version of Go are you using (go version)?

Theoretically: Go 1.14

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

macOS 10.14.6 Mojave

I cannot run any of the go tools to get any go information.

go env Output

$ go env

What did you do?

I removed the previous version of Golang using sudo rm -rf /usr/local/go, and then installed Go 1.14 - released 25.02.2020.

[1] I then first tried go version.
[2] Followed by go run path.go to a verified location.

What did you expect to see?

[1] I expected to see comforting words confirming that Go 1.14 was indeed installed.
[2] I expected my simple utility app path.go to be recompiled and to run.

What did you see instead?

~/code/go/src/github.com/carlca/utils/path master ❯ go run path.go                                                                                          ✱ ◼
SIGILL: illegal instruction
PC=0x1066040 m=0 sigcode=1

goroutine 1 [running, locked to thread]:
runtime.asyncPreempt()
	/usr/local/go/src/runtime/preempt_amd64.s:8 fp=0xc00005ae60 sp=0xc00005ae58 pc=0x1066040
crypto/rand.init()
	/usr/local/go/src/crypto/rand/util.go:26 fp=0xc00005ae68 sp=0xc00005ae60 pc=0x12055f0
runtime.doInit(0x1a82120)
	/usr/local/go/src/runtime/proc.go:5414 +0x8a fp=0xc00005ae98 sp=0xc00005ae68 pc=0x1043aca
runtime.doInit(0x1a80100)
	/usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc00005aec8 sp=0xc00005ae98 pc=0x1043a97
runtime.doInit(0x1a85560)
	/usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc00005aef8 sp=0xc00005aec8 pc=0x1043a97
runtime.doInit(0x1a82ae0)
	/usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc00005af28 sp=0xc00005aef8 pc=0x1043a97
runtime.doInit(0x1a81fe0)
	/usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc00005af58 sp=0xc00005af28 pc=0x1043a97
runtime.doInit(0x1a850c0)
	/usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc00005af88 sp=0xc00005af58 pc=0x1043a97
runtime.main()
	/usr/local/go/src/runtime/proc.go:190 +0x1ce fp=0xc00005afe0 sp=0xc00005af88 pc=0x103702e
runtime.goexit()
	/usr/local/go/src/runtime/asm_amd64.s:1373 +0x1 fp=0xc00005afe8 sp=0xc00005afe0 pc=0x10647d1

rax    0x1a82120
rbx    0xf
rcx    0x0
rdx    0x1a82198
rdi    0xc000112440
rsi    0x12055f0
rbp    0xc00005ae88
rsp    0xc00005ae58
r8     0x0
r9     0x0
r10    0x171acac
r11    0x1
r12    0xffffffffffffffff
r13    0x45
r14    0x44
r15    0x200
rip    0x1066040
rflags 0x10206
cs     0x2b
fs     0x0
gs     0x0
~/code/go/src/github.com/carlca/utils/path master ❯

The last 15 or so version upgrades to Golang have happened without a hitch. What is different this time?

[randall77]

Yuck.
I think we broke Darwin/amd64 on pre-AVX chips. VZEROUPPER needs a CPU feature detection guard.

@carlca, could you describe the machine you're running on? Apple menu, "About this Mac", the Processor line would do.

The bug was introduced for #37174, in CL 219131

@cherrymui

[carlca]

I suspect you are right. My machine, despite the fact I am running macOS 10.14.6 Mojave, is actually pretty ancient (early 2009), but has been tweaked to within an inch of its life (4,1 > 5,1 firmware patch and dosdude mojave patch).

I ran up against the AVX issue before with some music software (Native Instruments - Massive which would not run on my machine. Luckily I only tried the demo!).

Here are the specs...

[gopherbot]

Change https://golang.org/cl/221057 mentions this issue: runtime: guard VZEROUPPER on CPU feature

[gopherbot]

Change https://golang.org/cl/221058 mentions this issue: [release-branch.go1.14] runtime: guard VZEROUPPER on CPU feature

[dmitshur]

@gopherbot Please open a backport for 1.14. This is a regression in 1.14, and it is a serious problem (program doesn't run on affected hardware) without a workaround.

[gopherbot]

Backport issue(s) opened: #37478 (for 1.14).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.