On Wed, Jan 10, 2018 at 5:35 AM, Ian Lance Taylor <i...@golang.org> wrote: > On Tue, Jan 9, 2018 at 11:34 PM, Uros Bizjak <ubiz...@gmail.com> wrote: >>> This patch updates libgo to the Go1.10beta1 release. The final Go >>> 1.10 release is expected around February 1, so it's not clear how the >>> release timing is going to work with GCC 8. In any case this updates >>> GCC to something pretty close to the final Go 1.10 release. >> >> This patch introduces a bunch of new fails in gotools testsuite form >> non-split stack targets, e.g.: >> >> AIL: TestCgoSignalDeadlock >> crash_test.go:55: building testprogcgo []: exit status 2 >> # >> _/space/uros/gcc-svn/trunk/libgo/go/runtime/testdata/testprogcgo >> cc1: error: '-fsplit-stack' is not supported by this >> compiler configuration >> >> and also: >> >> # _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/gcc68255 >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> # >> _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/issue8756 >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> # >> _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/issue8828 >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> # >> _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/issue9026 >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> # >> _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/issue9510b >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> # >> _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test/issue9510a >> cc1: error: '-fsplit-stack' is not supported by this compiler configuration >> FAIL _/space/homedirs/uros/gcc-build/gotools/cgo-test-dir/misc/cgo/test >> [build failed] > > The go tool is trying to decide whether the C compiler supports the > -fsplit-stack option by running > gcc -fsplit-stack -c -x c - < /dev/null > On your system, what does that print, and what is the exit status?
(Where I say gcc above I really mean $CC if CC is set, which when running the tests will be the generated script gotools/check-gcc.) Ian