Recently text/template libgo test starts to compile for a very long time on alpha, probably due to some variable tracking explosion issue.
The problem is, that the compilation does not timeout after some time and can run for a very long time, or even indefinitely. Please introduce some kind of compilation timeout to libgo testsuite.
FYI: The compilation can finish in reasonable time with
(In reply to comment #0)
> FYI: The compilation can finish in reasonable time with
> -fno-var-tracking-assignments option.
The difference in compile time with this particular test was 38 minutes vs. a couple of minutes with -fno-var-tracking-assignment option.
The var-tracking problem is PR54402.
FYI, var-tracking just got a patch that could make this better.
> --- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2013-01-18 11:08:43 UTC ---
> FYI, var-tracking just got a patch that could make this better.
As reported in PR debug/54402, it does, but the main point of this PR is
that libgo testsuite don't time out compilations at all, irrespective of
the individual causes of slowness.