From: Siddhesh Poyarekar <sid@reserved-bit.com>
To: libc-alpha@sourceware.org
Subject: [COMMITTED] benchtests: Update README to include instructions for bench-build target
Date: Wed, 20 Apr 2016 05:30:00 -0000 [thread overview]
Message-ID: <20160420052953.GA18913@devel.intra.reserved-bit.com> (raw)
---
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
reply other threads:[~2016-04-20 5:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160420052953.GA18913@devel.intra.reserved-bit.com \
--to=sid@reserved-bit.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).