This is the mail archive of the
mailing list for the glibc project.
[COMMITTED] benchtests: Update README to include instructions for bench-build target
- From: Siddhesh Poyarekar <sid at reserved-bit dot com>
- To: libc-alpha at sourceware dot org
- Date: Wed, 20 Apr 2016 10:59:58 +0530
- Subject: [COMMITTED] benchtests: Update README to include instructions for bench-build target
- Authentication-results: sourceware.org; auth=none
ChangeLog | 3 +++
benchtests/README | 17 +++++++++++++++++
2 files changed, 20 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 9f9270b..74f57db 100644
@@ -1,5 +1,8 @@
2016-04-20 Siddhesh Poyarekar <email@example.com>
+ benchtests/README: Update README to include instructions on
+ using bench-build.
Makefile.in (bench-build): New target.
Rules (PHONY): Add bench-build target.
benchtests/Makefile (bench): Depend on bench-build.
diff --git a/benchtests/README b/benchtests/README
index 999d268..847df87 100644
@@ -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: