You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dashboard contains gigantic embedded strings in the source code, which cause the Go compiler to crash on windows/386. This needs to be reported and fixed upstream, but I'm opening this issue so we have something to track it with. I'll expand it with details as we manage to reproduce and report upstream.
Update 1: I can repro this locally. I need to run a 32bit build of Go to make it go boom, so the bug isn't with compiling to 386, rather compiling on 386.
>go version
go version go1.9.2 windows/386
>go env
set GOARCH=386
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=386
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\karalabe\go
set GORACE=
set GOROOT=C:\Work\go
set GOTOOLDIR=C:\Work\go\pkg\tool\windows_386
set GCCGO=gccgo
set GO386=sse2
set CC=gcc
set GOGCCFLAGS=-m32 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\karalabe\AppData\Local\Temp\go-build701140035=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
karalabe
changed the title
Go 1.9.2 compiler crashes building windows/386
386 version of Go 1.9.2 compiler crashes on building the dashboard
Dec 24, 2017
The dashboard contains gigantic embedded strings in the source code, which cause the Go compiler to crash on
windows/386
. This needs to be reported and fixed upstream, but I'm opening this issue so we have something to track it with. I'll expand it with details as we manage to reproduce and report upstream.TL;DR; https://ci.appveyor.com/project/ethereum/go-ethereum/build/master.4791/job/hcsxkgy0uh018j05#L136
Update 1: I can repro this locally. I need to run a 32bit build of Go to make it go boom, so the bug isn't with compiling to 386, rather compiling on 386.
Update 2: Apparently this also happens on Linux 386 (#15743), so it's not constrained to Windows, rather seemingly present on all 386 platforms.
The text was updated successfully, but these errors were encountered: