[FVTR] gccgo test is failing on pcc64 for AT >= 10.0 #143
Assignees
Labels
Comments
|
The cause of this issue is a misconfiguration of GCC that disables split-stack in all tuned libraries: I'm preparing a fix. |
tuliom
added a commit
to tuliom/advance-toolchain
that referenced
this issue
Jul 23, 2018
GCC cannot recognize the correct glibc version when configured without --with-glibc-version, causing split-stack to be disabled. The default builds already use this parameter, but the tuned libraries were left behind. This patch also improves the gccgo test to validate if split-stack was enabled in its shared libraries. Fixes issue advancetoolchain#143. Signed-off-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Closed
tuliom
added a commit
that referenced
this issue
Jul 27, 2018
GCC cannot recognize the correct glibc version when configured without --with-glibc-version, causing split-stack to be disabled. The default builds already use this parameter, but the tuned libraries were left behind. This patch also improves the gccgo test to validate if split-stack was enabled in its shared libraries. Fixes issue #143. Signed-off-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
tuliom
added a commit
to tuliom/advance-toolchain
that referenced
this issue
Aug 1, 2018
This patch backports a fix from AT 11.0 to AT 10.0 that enables split-stack in GCC tuned libraries. As both stage files became identical, the AT 11.0 file was replaced with a symlink. Closes advancetoolchain#143. Signed-off-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Merged
tuliom
changed the title
tuliom
added a commit
that referenced
this issue
Aug 3, 2018
This patch backports a fix from AT 11.0 to AT 10.0 that enables split-stack in GCC tuned libraries. As both stage files became identical, the AT 11.0 file was replaced with a symlink. Closes #143. Signed-off-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The gccgo test is failing on AT 11.0 when built for ppc64 (BE):
gccgo: power8: Running gccgo package test...
t^M
Hello!^M
fatal error: unexpected signal during runtime execution^M
gccgo: power8: gccgo test failed
By manually running we got the following errors:
./gopkgtest
Hello!
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=1 addr=1731642852816977920 pc=70367025496785]
goroutine 16 [running]:
runtime.dopanic
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/runtime/panic.go:832
runtime.throw
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/runtime/panic.go:758
runtime.sigpanic
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/runtime/signal_unix.go:241
runtime.sighandler
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/runtime/signal_sighandler.go:59
runtime.sigtrampgo
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/runtime/signal_unix.go:227
time.formatNano
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/time/format.go:403
time.AppendFormat.N9_time.Time
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/time/format.go:612
time.Format.N9_time.Time
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/time/format.go:457
time.String.N9_time.Time
/home/rzinsly/AT/tmp/at11.0-0-beta1.redhat-7_ppc64_ppc64/sources/gcc/libgo/go/time/format.go:428
main.main
/home/rzinsly/AT/tmp/fvtr/gccgo/testpkg.go:33
goroutine 17 [syscall]:
goroutine in C code; stack unavailable
goroutine 18 [finalizer wait]:
goroutine 19 [runnable]:
The text was updated successfully, but these errors were encountered: