Anton: I've done some experiments with the peano.go test and confirmed that gccgo on ppc is correctly configured to not use f-split-stack. It turns out the peano.go can't pass without split stacks. On gccgo/ppc64 the program crashes at a stack depth of
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x3fffb7722220 (LWP 24713)] 0x0000000010004e0c in main.is_zero () (gdb) bt #0 0x0000000010004e0c in main.is_zero () #1 0x00000000100051fc in main.count () #2 0x000000001000522c in main.count () ... #31380 0x000000001000522c in main.count () #31381 0x0000000010005854 in main.main () I think the peano example is just a straght 'fall off the stack' type error, it also generates a slightly different ubuntu@winton-02:~/go/test$ ./a.out Segmentation fault (core dumped) ubuntu@winton-02:~/go/test$ dmesg | tail -n1 [501663.078093] a.out[25679]: bad frame in setup_rt_frame: 000000c20ffaf0e0 nip 0000000010004e0c lr 00000000100051fc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304754 Title: gccgo on ppc64el using split stacks when not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1304754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs