From: Nicholas Nethercote <njn@valgrind.org>
Date: Fri, 2 Jun 2006 23:59:40 +0000 (+0000)
Subject: wibbles
X-Git-Tag: svn/VALGRIND_3_2_0~7
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8c294cb0283743f0694824082260d12fb10dffc4;p=thirdparty%2Fvalgrind.git

wibbles



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5952
---

diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index 7835028399..9c63e4b284 100644
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -1,7 +1,6 @@
 
 Building and not installing it
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
 To run Valgrind without having to install it, run coregrind/valgrind
 with the VALGRIND_LIB environment variable set, where <dir> is the root
 of the source tree (and must be an absolute path).  Eg:
@@ -33,11 +32,11 @@ file.  Eg:
   perl tests/vg_regtest memcheck/tests/badfree
 
 
-Running the performance suite
+Running the performance tests
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To build and run the whole performance suite, run "make [--quiet] perf".
+To build and run all the performance tests, run "make [--quiet] perf".
 
-To run a subset of the regression tests, execute:
+To run a subset of the performance suite, execute:
 
   perl perf/vg_perf <name>
 
@@ -49,10 +48,10 @@ file.  Eg:
   perl perf/vg_perf perf/bz2.vgperf
   perl perf/vg_perf perf/bz2
 
-To compare multiple versions of Valgrind, use the --vg= options multiple
+To compare multiple versions of Valgrind, use the --vg= option multiple
 times.  For example, if you have two Valgrinds next to each other, one in
-trunk1/ and one in trunk2/, from either trunk1/ or trunk2/ do this to
-compare them on the entire suite:
+trunk1/ and one in trunk2/, from within either trunk1/ or trunk2/ do this to
+compare them on all the performance tests:
 
   perl perf/vg_perf --vg=../trunk1 --vg=../trunk2 perf/