diff options
author | Siddhesh Poyarekar <sid@reserved-bit.com> | 2016-04-20 10:23:28 +0530 |
---|---|---|
committer | Siddhesh Poyarekar <sid@reserved-bit.com> | 2016-04-20 10:23:28 +0530 |
commit | a00d3f4a8c19547b4050889965d9a2a93429ae51 (patch) | |
tree | 1e796b1032343a4f7ddb947f4ed90c8daf0180b0 /benchtests | |
parent | 6f8222a1c52a9e577925b90d16b95be10ef50596 (diff) | |
download | glibc-a00d3f4a8c19547b4050889965d9a2a93429ae51.tar.gz |
New make target to only build benchmark binaries
For situations where we are cross-building or where we want to avoid
building on the target system, we want a way to only build benchmarks
and then copy them over to the target system to run them. I have also
added a simple enhancement for the 'bench' target where all benchmark
binaries are built and then the benchmarks executed.
Tested on arm.
Makefile.in (bench-build): New target.
Rules (PHONY): Add bench-build target.
benchtests/Makefile (bench): Depend on bench-build.
(bench-build): New target.
Diffstat (limited to 'benchtests')
-rw-r--r-- | benchtests/Makefile | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/benchtests/Makefile b/benchtests/Makefile index 61077ea9b6..a05974ec85 100644 --- a/benchtests/Makefile +++ b/benchtests/Makefile @@ -128,7 +128,10 @@ bench-clean: rm -f $(binaries-bench-malloc) $(addsuffix .o,$(binaries-bench-malloc)) rm -f $(timing-type) $(addsuffix .o,$(timing-type)) -bench: $(timing-type) $(gen-locales) bench-set bench-func bench-malloc +bench: $(timing-type) $(gen-locales) bench-build bench-set bench-func \ + bench-malloc +# Target to only build the benchmark without running it. +bench-build: $(binaries-bench) $(binaries-benchset) $(binaries-bench-malloc) bench-set: $(binaries-benchset) for run in $^; do \ |