Skip to content

Commit e84f79e

Browse files
committed
[libc++][docs] Use --show-all in the sample command-line to run benchmarks
It's really not useful at all to run benchmarks without --show-all since you don't get the benchmark output. And since --show-all is the suggested default way to run benchmarks, it's not necessary anymore to mention it right below.
1 parent 22774bb commit e84f79e

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

libcxx/docs/TestingLibcxx.rst

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -452,12 +452,7 @@ when running the benchmarks. For example,
452452

453453
.. code-block:: bash
454454
455-
$ libcxx/utils/libcxx-lit <build> -sv libcxx/test/benchmarks/string.bench.cpp --param optimization=speed
456-
457-
If you want to see where a benchmark is located (e.g. you want to store the executable
458-
for subsequent analysis), you can print that information by passing ``--show-all`` to
459-
``lit``. That will print the command-lines being executed, which includes the location
460-
of the executable created for that benchmark.
455+
$ libcxx/utils/libcxx-lit <build> libcxx/test/benchmarks/string.bench.cpp --show-all --param optimization=speed
461456
462457
Note that benchmarks are only dry-run when run via the ``check-cxx`` target since
463458
we only want to make sure they don't rot. Do not rely on the results of benchmarks

0 commit comments

Comments
 (0)