https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> --- The Go testsuite is intended to have timeouts for all tests. The test gcc/testsuite/go.test/test/fixedbugs/issue19182.go is just passed off to the TCL function go-torture-execute. Running the executable gcc/testsuite/go/issue19182.x is the "execute" part of the test. go-torture-execute calls the TCL function go_load to run the test. My assumption, which may well be wrong, is that a TCL function like go_load applies a timeout by default. I'm not even sure where go_load is defined, but it clearly does exist. I'm still baffled by how all the DejaGNU code works. It's odd that issue19182.x keeps running. The test itself is intended to be self-limiting. I'm not sure what is going on there.
