This is the mail archive of the
glibc-cvs@sourceware.org
mailing list for the glibc project.
GNU C Library master sources branch master updated. glibc-2.23-215-gbfdda21
- From: siddhesh at sourceware dot org
- To: glibc-cvs at sourceware dot org
- Date: 20 Apr 2016 05:29:11 -0000
- Subject: GNU C Library master sources branch master updated. glibc-2.23-215-gbfdda21
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via bfdda211c6b082d12ec448a5a65bfba02e208b98 (commit)
from 68e9d3c6889aa3594b6722e420813fa120c9d612 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=bfdda211c6b082d12ec448a5a65bfba02e208b98
commit bfdda211c6b082d12ec448a5a65bfba02e208b98
Author: Siddhesh Poyarekar <sid@reserved-bit.com>
Date: Wed Apr 20 10:58:20 2016 +0530
benchtests: Update README to include instructions for bench-build target
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:
===============================
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 3 +++
benchtests/README | 17 +++++++++++++++++
2 files changed, 20 insertions(+), 0 deletions(-)
hooks/post-receive
--
GNU C Library master sources