diff options
| -rw-r--r-- | open_issues/gcc.mdwn | 19 |
1 files changed, 3 insertions, 16 deletions
diff --git a/open_issues/gcc.mdwn b/open_issues/gcc.mdwn index 6c14fdd4..a2a67632 100644 --- a/open_issues/gcc.mdwn +++ b/open_issues/gcc.mdwn @@ -843,22 +843,6 @@ min on coulomb.SCHWINGE. <http://gcc.gnu.org/install/test.html> -Testing on GNU/Hurd is blocked on -[[fork_mach_port_mod_refs_ekern_urefs_owerflow]]. - -TODO. On GNU/Hurd, it is advisable to reboot after having built and installed -GCC, before running the testsuite, as otherwise there seems to be a tendency -that the system crashes during the `gcc.c-torture/compile/limits-structnest.c` -tests, which are rather memory hungry, see [[!message-id -"87bol6aixd.fsf@schwinge.name"]]. Likewise, it also seems advisable to add -further reboots in between, that is, separate `make check`'s `check-host` into -several separate runs, and then one for `check-target` (see -`[build]/Makefile:do-check`, `[build]/gcc/Makefile:CHECK_TARGETS`), as -otherwise there seems to be a tendency for the system crashing sooner or later. -(Running `check-host` accumulates to something like 44 hours worth of -forking/execing of GCC and testcases.) On GNU/Linux we run it in one go, so -that we'll catch any fundamental rearrangements of/additions to the testsuites. - kepler.SCHWINGE: $ make -k check 2>&1 | tee log_test @@ -911,6 +895,9 @@ coulomb.SCHWINGE. ## Analysis + A lot of the failures are due to gcc's unwind support not knowing about signal trampoline on GNU/Hurd, this is a TODO. + + $ toolchain/logs/process gcc test * PTYs |