diff options
author | Richard Sandiford <richard.sandiford@linaro.org> | 2017-11-05 17:19:35 +0000 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@linaro.org> | 2017-11-05 17:19:35 +0000 |
commit | 648f8fc59b2cc39abd24f4c22388b346cdebcc31 (patch) | |
tree | 3a07eccc4c22b265261edd75c9ec3910d9c626f5 /gcc/jit/docs | |
parent | 7bef5b82e4109778a0988d20e19e1ed29dadd835 (diff) | |
parent | 8c089b5c15a7b35644750ca393f1e66071ad9aa9 (diff) | |
download | gcc-648f8fc59b2cc39abd24f4c22388b346cdebcc31.tar.gz |
Merge trunk into sve
Diffstat (limited to 'gcc/jit/docs')
-rw-r--r-- | gcc/jit/docs/_build/texinfo/libgccjit.texi | 18 | ||||
-rw-r--r-- | gcc/jit/docs/internals/index.rst | 10 |
2 files changed, 21 insertions, 7 deletions
diff --git a/gcc/jit/docs/_build/texinfo/libgccjit.texi b/gcc/jit/docs/_build/texinfo/libgccjit.texi index 344c93e4ccf..a3b206f2dd4 100644 --- a/gcc/jit/docs/_build/texinfo/libgccjit.texi +++ b/gcc/jit/docs/_build/texinfo/libgccjit.texi @@ -19,7 +19,7 @@ @copying @quotation -libgccjit 8.0.0 (experimental 20171004), October 04, 2017 +libgccjit 8.0.0 (experimental 20171031), October 31, 2017 David Malcolm @@ -15016,7 +15016,12 @@ jit/build/gcc/testsuite/jit/jit.log @noindent -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 +@geindex PRESERVE_EXECUTABLES +@geindex environment variable; PRESERVE_EXECUTABLES +@code{PRESERVE_EXECUTABLES} +in the environment. If so, they can then be seen as: @example jit/build/gcc/testsuite/jit/*.exe @@ -15029,7 +15034,9 @@ which can be run independently. You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.: @example -[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" @end example @noindent @@ -15056,7 +15063,10 @@ and once a test has been compiled, you can debug it directly: @subsection Running under valgrind -The jit testsuite detects if RUN_UNDER_VALGRIND is present in the +The jit testsuite detects if +@geindex RUN_UNDER_VALGRIND +@geindex environment variable; RUN_UNDER_VALGRIND +@code{RUN_UNDER_VALGRIND} is present in the environment (with any value). If it is present, it runs the test client code under valgrind@footnote{http://valgrind.org}, specifcally, the default diff --git a/gcc/jit/docs/internals/index.rst b/gcc/jit/docs/internals/index.rst index cadf36283ef..4ad7f61f774 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 |