https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom de Vries from comment #2) > (In reply to Richard Biener from comment #1) > > Doesn't whatever driver/library API we use from libgomp to invoke workloads > > report actual errors? Maybe we need to improve there. > > Good point, it reported some form of timeout. I'll post the exact form once > I reproduce. It's: ... Execution timeout is: 300 spawn [open ...]^M libgomp: cuStreamSynchronize error: the launch timed out and was terminated FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/parallel-dims.c -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -foffload=nvptx-none -O0 execution test ... Googling a bit about this error message ( https://forums.developer.nvidia.com/t/need-to-remove-timeouts-and-the-launch-timed-out-and-was-terminated-message/16741/2 ) shows that running a display manager sets a 5/10 seconds watchdog timer on any kernel.
