> Date: Wed, 14 Jan 2026 00:58:58 +0000 (UTC)
> From: Joseph Myers <[email protected]>

> The simulate-thread tests exit early in cross and remote cases.  Apply
> fixes similar to (but affecting separate code) those recently posted
> for the guality tests: do not use [transform gdb] since that's a cross
> GDB and the tests expect to run GDB on the target, test existence on
> the target not the build system, and copy required files to the target
> (deleting them later).
> 
> Tested for x86_64-pc-linux-gnu to make sure native testing isn't
> broken, and with cross to aarch64-linux.
> 
>       * lib/gcc-dg.exp (gdb-exists): Do not use [transform gdb].  Run
>       selected GDB with -v on target rather than testing for existence
>       on build system.
>       * lib/gcc-simulate-thread.exp (simulate-thread): Do not return
>       early for non-native and remote.  Download executable and GDB
>       command file to target before running GDB there, and delete when
>       closing target.

TL;DR: please consider augmenting your testing to check a
*-elf (bare-iron) target against a simulator and/or a
bare-iron board; a cross-setup that can't run gdb.
Also consider grepping your build log for "^ERROR" as part
of the regression checking.

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.
...
Running /src/gcc/testsuite/g++.dg/guality/guality.exp ...
ERROR: Remote execution for simulators not implemented.
...
Running /src/gcc/testsuite/g++.dg/simulate-thread/simulate-thread.exp ...
ERROR: Remote execution for simulators not implemented.
...
Running /src/gcc/testsuite/gfortran.dg/guality/guality.exp ...
ERROR: Remote execution for simulators not implemented.

I started grepping the build logs for "^ERROR" in my
autotester scripts, since that's a clear indicator of an
error in the testsuite framework; one of the really annoying
kind, that skips part of the testsuite, aborting the .exp
processing (IIRC).  While those tests would probably be
skipped for this target anyway, such a conclusion would
require manual intervention and investigation.

Bisected to commit r16-6780-g620c85fb709d27, and I believe
r16-6781 extended the problem.

$ runtest --version
DejaGnu version 1.6.2
Expect version  5.45.4
Tcl version     8.6

Also seen for "DejaGnu version 1.6.3".

Please be mindful about cross-targets that can't run gdb.
I have not yet entered a bug-report for this.

brgds, H-P

Reply via email to