diff options
| author | David Malcolm <dmalcolm@redhat.com> | 2017-10-31 20:40:10 +0000 |
|---|---|---|
| committer | David Malcolm <dmalcolm@gcc.gnu.org> | 2017-10-31 20:40:10 +0000 |
| commit | 77f4ead72e55094fca78530bff75f83eb0faadbd (patch) | |
| tree | 948ebc9e41f6bf42946a6d4cfebf912145df61fd /gcc/jit/docs/internals | |
| parent | 84ffba1283c323e559d487f5a44012e2481f7c85 (diff) | |
| download | gcc-77f4ead72e55094fca78530bff75f83eb0faadbd.zip gcc-77f4ead72e55094fca78530bff75f83eb0faadbd.tar.gz gcc-77f4ead72e55094fca78530bff75f83eb0faadbd.tar.bz2 | |
jit: add a way to preserve testsuite executables
gcc/jit/ChangeLog:
* docs/internals/index.rst (Running the test suite): Document
PRESERVE_EXECUTABLES.
(Running under valgrind): Add markup to RUN_UNDER_VALGRIND.
* docs/_build/texinfo/libgccjit.texi: Regenerate.
gcc/testsuite/ChangeLog:
* jit.dg/jit.exp (jit-dg-test): If PRESERVE_EXECUTABLES is set in
the environment, don't delete the generated executable.
From-SVN: r254282
Diffstat (limited to 'gcc/jit/docs/internals')
| -rw-r--r-- | gcc/jit/docs/internals/index.rst | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/gcc/jit/docs/internals/index.rst b/gcc/jit/docs/internals/index.rst index cadf362..4ad7f61 100644 --- a/gcc/jit/docs/internals/index.rst +++ b/gcc/jit/docs/internals/index.rst @@ -103,7 +103,9 @@ and detailed logs in: jit/build/gcc/testsuite/jit/jit.log -The test executables can be seen as: +The test executables are normally deleted after each test is run. For +debugging, they can be preserved by setting :envvar:`PRESERVE_EXECUTABLES` +in the environment. If so, they can then be seen as: .. code-block:: console @@ -115,7 +117,9 @@ You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTES .. code-block:: console - [gcc] $ make check-jit RUNTESTFLAGS="-v -v -v jit.exp=test-factorial.c" + [gcc] $ PRESERVE_EXECUTABLES= \ + make check-jit \ + RUNTESTFLAGS="-v -v -v jit.exp=test-factorial.c" and once a test has been compiled, you can debug it directly: @@ -130,7 +134,7 @@ and once a test has been compiled, you can debug it directly: Running under valgrind ********************** -The jit testsuite detects if RUN_UNDER_VALGRIND is present in the +The jit testsuite detects if :envvar:`RUN_UNDER_VALGRIND` is present in the environment (with any value). If it is present, it runs the test client code under `valgrind <http://valgrind.org>`_, specifcally, the default |