https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119692
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ro at gcc dot gnu.org
--- Comment #8 from Rainer Orth <ro at gcc dot gnu.org> ---
The last commit made things worse on sparc-sun-solaris2.11: since that one
(dg-timeout 10) I regularly get
WARNING: libgomp.c++/target-exceptions-bad_cast-1.C (test for excess errors)
program timed out.
FAIL: libgomp.c++/target-exceptions-bad_cast-1.C (test for excess errors)
UNRESOLVED: libgomp.c++/target-exceptions-bad_cast-1.C compilation failed to
produce executable
UNRESOLVED: libgomp.c++/target-exceptions-bad_cast-1.C scan-tree-dump-times
optimized "gimple_call <__cxa_bad_cast, " 1
Before that, the test had no issue. Compiling the test on an unloaded system
usually takes less than 1 sec, but when fully loaded, times can go up.
Absolute timeouts are almost always wrong: e.g. they don't take increased
default timeouts into account (not the case on the system in question). That's
what dg-timeout-factor is for, although so far it's mostly been used to
increase
timeouts for slow tests.
