https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64876
Bug ID: 64876
Summary: Regressions in gcc-testresults for powerpc64 gccgo in
5.0 due to change for static chain for closures
(219776)
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at us dot ibm.com
CC: cmang at google dot com
Target: powerpc64
Many new failures appear in gcc-testresults for gccgo on powerpc64 after the
change was added to use the static chain for closures. Regressions do not
occur with powerpc64le. (Probably due to the different ABIs?) There are 30+
regressions in the go tests and 100+ regressions in the libgo testsuite.
The first gcc-testresults page with these regressions is:
https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg01797.html
The failures I've seen have a message with a signal 11:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x8]
goroutine 16 [running]:
main.$nested0
/home/boger/gccgo.work/r219749/src/gcc/testsuite/go.test/test/escape.go:152
main.for_escapes3
/home/boger/gccgo.work/r219749/src/gcc/testsuite/go.test/test/escape.go:155
main.main
/home/boger/gccgo.work/r219749/src/gcc/testsuite/go.test/test/escape.go:204
created by main
/home/boger/gccgo.work/r219749/bld/../src/libgo/runtime/go-main.c:42
FAIL: go.test/test/escape.go execution, -O2 -g
