* [COMMITTED] benchtests: Update README to include instructions for bench-build target
@ 2016-04-20 5:30 Siddhesh Poyarekar
0 siblings, 0 replies; only message in thread
From: Siddhesh Poyarekar @ 2016-04-20 5:30 UTC (permalink / raw)
To: libc-alpha
---
ChangeLog | 3 +++
benchtests/README | 17 +++++++++++++++++
2 files changed, 20 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 9f9270b..74f57db 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
2016-04-20 Siddhesh Poyarekar <sid@reserved-bit.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
--- 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:
===============================
--
2.5.5
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-04-20 5:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-20 5:30 [COMMITTED] benchtests: Update README to include instructions for bench-build target Siddhesh Poyarekar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).