about summary refs log tree commit diff
path: root/benchtests
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <sid@reserved-bit.com>2016-04-20 10:58:20 +0530
committerSiddhesh Poyarekar <sid@reserved-bit.com>2016-04-20 10:58:20 +0530
commitbfdda211c6b082d12ec448a5a65bfba02e208b98 (patch)
treeaafdd354c2fecc9b447e2056f448479189c1cb27 /benchtests
parent68e9d3c6889aa3594b6722e420813fa120c9d612 (diff)
downloadglibc-bfdda211c6b082d12ec448a5a65bfba02e208b98.tar.gz
glibc-bfdda211c6b082d12ec448a5a65bfba02e208b98.tar.xz
glibc-bfdda211c6b082d12ec448a5a65bfba02e208b98.zip
benchtests: Update README to include instructions for bench-build target
Diffstat (limited to 'benchtests')
-rw-r--r--benchtests/README17
1 files changed, 17 insertions, 0 deletions
diff --git a/benchtests/README b/benchtests/README
index 999d268cf8..847df87c96 100644
--- a/benchtests/README
+++ b/benchtests/README
@@ -34,6 +34,23 @@ the benchmark to use clock_gettime by invoking make as follows:
 
 Again, one must run `make bench-clean' before changing the measurement method.
 
+Running benchmarks on another target:
+====================================
+
+If the target where you want to run benchmarks is not capable of building the
+code or you're cross-building, you could build and execute the benchmark in
+separate steps.  On the build system run:
+
+  $ make bench-build
+
+and then copy the source and build directories to the target and run the
+benchmarks from the build directory as usual:
+
+  $ make bench
+
+make sure the copy preserves timestamps by using either rsync or scp -p
+otherwise the above command may try to build the benchmark again.
+
 Adding a function to benchtests:
 ===============================