|
From: | Svante Signell |
Subject: | Hurd port for gcc go PATCH 1-4(23) |
Date: | Fri, 25 Nov 2016 20:57:26 +0100 |
Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-6 (6-6.2.1-5). The first three patches are Debian-specific: * debian_rules.defs.diff: Enables build of gccgo for GNU/Hurd Define patches for the generated series file: * debian_rules.patch.diff: Enables split-stack support. * debian_rules.patch.diff: Does not enable split-stack support. * src_gcc_config_i386_gnu.h.diff: Enable split-stack support The test suite results are as follows: Without split-stack support: === go Summary === # of expected passes 7359 # of unexpected failures 7 # of expected failures 1 # of untested testcases 10 # of unsupported tests 2 === libgo Summary === # of expected passes 121 # of unexpected failures 13 With split-stack support: === go Summary === # of expected passes 7366 # of unexpected failures 8 # of expected failures 1 # of untested testcases 6 # of unsupported tests 2 === libgo Summary === # of expected passes 120 # of unexpected failures 14 All failing go tests and more than half of the libgo tests are runtime errors due to exception handling not working as expected: Aborted runtime_sighandler ... fatal error: unexpected signal during runtime execution panic: runtime error: invalid memory address or nil pointer dereference The above problems are probably due to some remaining issues in gnumach/hurd/glibc to be solved. According to Samuel Thibault these problems can be handled late when the patches are accepted upstream or in Debian gcc. Another more annoying gnumch/hurd/glibc bug is that the built program go (go-6 in Debian) gets killed when executed from the shell vi path, but not when issued directly: /usr/bin/go-6 works fine. go-6 Segmentation fault (core dumped) gdb /usr/bin/go-6 -c ./core warning: Unexpected size of section `.reg2/16883' in core file. Core was generated by `go-6'. Program terminated with signal SIGSEGV, Segmentation fault. warning: Unexpected size of section `.reg2/16883' in core file. #0 0x01e854ae in ?? () (gdb) bt #0 0x01e854ae in ?? () #1 0x00000000 in ?? () Nevertheless, it seems like not so much is left for gccgo working properly on GNU/Hurd. Thanks!
debian_rules.defs.diff
Description: Text Data
debian_rules.patch.diff
Description: Text Data
debian_rules.patch.diff1
Description: Text Data
src_gcc_config_i386_gnu.h.diff
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |