Index: docs/quickstart.rst =================================================================== --- docs/quickstart.rst +++ docs/quickstart.rst @@ -62,7 +62,7 @@ #. Execute the ``lnt runtest test-suite`` test producer, point it at the test suite and the compiler you want to test:: - $ lnt runtest test-suite \ + lnt runtest test-suite \ --sandbox /tmp/BAR \ --cc ~/llvm.obj.64/Release+Asserts/bin/clang \ --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \ Index: docs/tests.rst =================================================================== --- docs/tests.rst +++ docs/tests.rst @@ -66,8 +66,8 @@ Running the test-suite via CMake and lit uses a different LNT test:: - $ rm -rf /tmp/BAR - $ lnt runtest test-suite \ + rm -rf /tmp/BAR + lnt runtest test-suite \ --sandbox /tmp/BAR \ --cc ~/llvm.obj.64/Release+Asserts/bin/clang \ --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \ @@ -269,7 +269,7 @@ typical command line using this for evaluating the performance of generated code looks something like the following:: - $ lnt runtest test-suite \ + lnt runtest test-suite \ --sandbox SANDBOX \ --cc ~/bin/clang \ --use-cmake=/usr/local/bin/cmake \ @@ -304,7 +304,7 @@ Full example using ``llvmlab`` to debug a performance improvement:: - $ llvmlab bisect --min-rev=261265 --max-rev=261369 \ + llvmlab bisect --min-rev=261265 --max-rev=261369 \ lnt runtest test-suite \ --cc '%(path)s/bin/clang' \ --sandbox SANDBOX \ @@ -322,7 +322,7 @@ The test-suite module can produce a diagnostic report which might be useful for figuring out what is going on with a benchmark:: - $ lnt runtest test-suite \ + lnt runtest test-suite \ --sandbox /tmp/BAR \ --cc ~/llvm.obj.64/Release+Asserts/bin/clang \ --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \ @@ -349,7 +349,7 @@ An example command line for cross-compiling on an X86 machine, targeting AArch64 linux, is:: - $ lnt runtest test-suite \ + lnt runtest test-suite \ --sandbox SANDBOX \ --test-suite /work/llvm-test-suite \ --use-lit lit \