[libcxx-commits] [libcxx] b285bac - [libc++][NFC] In documentation, fix path to benchmark that has now moved

[Louis Dionne via libcxx-commits]

Author: Louis Dionne
Date: 2025-09-29T09:46:21-04:00
New Revision: b285bac972354f961e611b46ee9fde1b3d760730

URL: https://github.com/llvm/llvm-project/commit/b285bac972354f961e611b46ee9fde1b3d760730
DIFF: https://github.com/llvm/llvm-project/commit/b285bac972354f961e611b46ee9fde1b3d760730.diff

LOG: [libc++][NFC] In documentation, fix path to benchmark that has now moved

Added: 
    

Modified: 
    libcxx/docs/TestingLibcxx.rst

Removed: 
    


################################################################################
diff  --git a/libcxx/docs/TestingLibcxx.rst b/libcxx/docs/TestingLibcxx.rst
index 227791031bab0..6171629185af2 100644
--- a/libcxx/docs/TestingLibcxx.rst
+++ b/libcxx/docs/TestingLibcxx.rst
@@ -482,7 +482,7 @@ when running the benchmarks. For example,
 
 .. code-block:: bash
 
-  $ libcxx/utils/libcxx-lit <build> libcxx/test/benchmarks/string.bench.cpp --show-all --param optimization=speed
+  $ libcxx/utils/libcxx-lit <build> libcxx/test/benchmarks/containers/string.bench.cpp --show-all --param optimization=speed
 
 Note that benchmarks are only dry-run when run via the ``check-cxx`` target since
 we only want to make sure they don't rot. Do not rely on the results of benchmarks
@@ -504,7 +504,7 @@ more benchmarks, as usual:
 .. code-block:: bash
 
   $ cmake -S runtimes -B <build> [...]
-  $ libcxx/utils/libcxx-lit <build> libcxx/test/benchmarks/string.bench.cpp --param optimization=speed
+  $ libcxx/utils/libcxx-lit <build> libcxx/test/benchmarks/containers/string.bench.cpp --param optimization=speed
 
 Then, get the consolidated benchmark output for that run using ``consolidate-benchmarks``: