Skip to content

Commit 60f654c

Browse files
committed
README: Document usage of RUNTESTFLAGS for make check
Let's document how to use the environment variable RUNTESTFLAGS for selecting the tests that should be executed. Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
1 parent 60c5267 commit 60f654c

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

README.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -210,6 +210,25 @@ Note:
210210
- spike only support rv64* bare-metal/elf toolchain.
211211
- gdb simulator only support bare-metal/elf toolchain.
212212

213+
#### Selecting the tests to run in GCC's regression test suite
214+
215+
By default GCC will execute all tests of its regression test suite.
216+
While running them in parallel (e.g. `make -j$(nproc) report`) will
217+
significanlty speed up the execution time on multi-processor systems,
218+
the required time for executing all tests is usually too high for
219+
typical development cycles. Therefore GCC allows to select the tests
220+
that are being executed using the environment variable `RUNTESTFLAGS`.
221+
222+
To restrict a test run to only RISC-V specific tests
223+
the following command can be used:
224+
225+
RUNTESTFLAGS="riscv.exp" make report
226+
227+
To to restrict a test run to only RISC-V specific tests with match the
228+
pattern "zb*.c" and "sm*.c" the following command can be used:
229+
230+
RUNTESTFLAGS="riscv.exp=zb*.c\ sm*.c" make report
231+
213232
#### Testing GCC, Binutils, and glibc of a Linux toolchain
214233

215234
The default Makefile target to run toolchain tests is `report`.

0 commit comments

Comments
 (0)