> Date: Thu, 15 Jan 2026 22:25:15 +0000 (UTC) > From: Joseph Myers <[email protected]> > On Thu, 15 Jan 2026, Hans-Peter Nilsson wrote: > > > > Date: Thu, 15 Jan 2026 22:09:09 +0000 (UTC) > > > From: Joseph Myers <[email protected]> > > > 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. > > > > [...] > > > > Either way, changes to the gcc test-suite needs to cope with > > such warts, when possible. It's not proper to make a change > > like this that tickles an erroneous corner case (if it > > indeed is), then push the blame. > > It does cope: it skips the tests that can't work on such a target and > continues with the rest of the testsuite. It simply shows an ERROR that > indicates a possible bug in the test machinery - in this case, a bug in > the board file that can best be fixed in the board file.
That's pushing the blame! The board file does not emit an error; that comes from somewhere in the middle of dejagnu. See for yourself: cris-sim.exp is in recent dejagnu releases. I believe the same thing happens for other *-sim.exp. The gcc testsuite needs to handle this without causing an ERROR to be emitted. brgds, H-P
