25aaf0cb7f
As our set of multiarch tests has grown the practice of running every plugin with every test is becoming unsustainable. If we switch to ensuring every test gets run with at least one plugin we can speed things up. Some plugins do need to be run with specific tests (for example the memory instrumentation test). We can handle this by manually adding them to EXTRA_RUNS. We also need to wrap rules in a CONFIG_PLUGIN test so we don't enable the runs when plugins are not enabled. Reviewed-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-ID: <20250725154517.3523095-12-alex.bennee@linaro.org> |
||
|---|---|---|
| .. | ||
| aarch64 | ||
| aarch64_be | ||
| alpha | ||
| arm | ||
| hexagon | ||
| hppa | ||
| i386 | ||
| loongarch64 | ||
| m68k | ||
| minilib | ||
| mips | ||
| multiarch | ||
| openrisc | ||
| plugins | ||
| ppc64 | ||
| ppc64le | ||
| riscv64 | ||
| s390x | ||
| sh4 | ||
| tricore | ||
| x86_64 | ||
| xtensa | ||
| xtensaeb | ||
| Makefile.target | ||
| README | ||
This directory contains various interesting guest binaries for regression testing the Tiny Code Generator doing system and user-mode emulation. The multiarch directory contains shared code for tests that can be built for all guest architectures. Architecture specific code can be found in their respective directories. System mode tests will be under the "system" subdirectories. GDB scripts for exercising the gdbstub on specific tests will be found under the "gdbstb" subdirectories. See the developer guide for more instructions on "make check-tcg"