docs/internals/index.rst

64   running the test suite:
68 …xgcc: error: /home/david/jit/src/gcc/testsuite/jit.dg/test-quadratic.cc: C++ compiler not installe…
69     c++: error trying to exec 'cc1plus': execvp: No such file or directory
98   jit/build/gcc/testsuite/jit/jit.sum
151 ``test-sum-of-squares.c`` under valgrind, showing an issue:
157         RUNTESTFLAGS="-v -v -v jit.exp=test-sum-of-squares.c"
166   $ less testsuite/jit/jit.sum
168 …XFAIL: jit.dg/test-sum-of-squares.c: test-sum-of-squares.c.exe.valgrind.txt: definitely lost: 8 by…
169 …XFAIL: jit.dg/test-sum-of-squares.c: test-sum-of-squares.c.exe.valgrind.txt: unsuppressed errors: 1
172   $ less testsuite/jit/test-sum-of-squares.c.exe.valgrind.txt
175 When running under valgrind, it's best to have configured gcc with
181 When running client code against a locally-built libgccjit, three
186    `libgccjit.so` is dynamically linked into client code, so if running
211   subdirectory of the build tree for running the testsuite, and for ease
226   Hence if running directly from a locally-built copy (without installing),
297 * ``libgccjit.c`` implements the API entrypoints.  It performs error
339 error.  If this *does* happen, the root cause should be isolated (perhaps
343 close as possible to the error; failing that, a good place is within
389     not running them).   A new API entrypoint
406 expects jit testcases to begin with ``test-``, or ``test-error-`` (for a
407 testcase that generates an error on a :c:type:`gcc_jit_context`).
417     successful tests in one process, each one running in a different
435 running ``make texinfo`` within ``SRCDIR/gcc/jit/docs``.   Don't do this