On Thu, 15 Jan 2026, Hans-Peter Nilsson wrote: > At r16-6786-g109fae9d4df664 I see, for cris-elf, running > tests against the cris-sim dejagnu baseboard: > > Running /src/gcc/testsuite/gcc.dg/guality/guality.exp ... > ERROR: Remote execution for simulators not implemented. > ... > Running /src/gcc/testsuite/gcc.dg/simulate-thread/simulate-thread.exp ... > ERROR: Remote execution for simulators not implemented.
I think this is a bug in the board files not the GCC testsuite. As far as I can tell, the DejaGnu board file interface doesn't include a direct way to query "is remote_exec supported for this board?", which means it's natural to try remote_exec and see if it returns success or failure (in the form of a list whose first value is the exit status of the program, -1 for exec failure, and whose second value is the output text). So a board file with no remote_exec support should have a <board>_exec that returns a list with first element -1 and second element text such as the "Remote execution for simulators not implemented." - it should *not* put that text as an ERROR in the logs. Given a board file that follows the board file interface to report <board>_exec failure without an ERROR, the [gdb-exists] conditional in simulate-thread.exp would return 0 and so prevent those tests from running, without an ERROR. Likewise, in guality.exp, the report_gdb call would no longer produce an ERROR, and the check_guality call should then fail for any target not supporting interfaces such as popen, or where GDB isn't installed and so popen of gdb fails, and so prevent those tests from running. -- Joseph S. Myers [email protected]
