aboutsummaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@gcc.gnu.org>2001-07-26 08:41:48 +0200
committerAndreas Jaeger <aj@gcc.gnu.org>2001-07-26 08:41:48 +0200
commita6ed70ef1df6e0d2e900d976513c4a2c3b439b8a (patch)
treea8e446768d8518da2629c3caaa9f9b73d86ede75 /contrib
parentcef0d199d24feb707b86db0ad2991823b276cd1a (diff)
downloadgcc-a6ed70ef1df6e0d2e900d976513c4a2c3b439b8a.zip
gcc-a6ed70ef1df6e0d2e900d976513c4a2c3b439b8a.tar.gz
gcc-a6ed70ef1df6e0d2e900d976513c4a2c3b439b8a.tar.bz2
* analyze_brprob: Fix documentation.
From-SVN: r44381
Diffstat (limited to 'contrib')
-rw-r--r--contrib/ChangeLog7
-rwxr-xr-xcontrib/analyze_brprob4
2 files changed, 8 insertions, 3 deletions
diff --git a/contrib/ChangeLog b/contrib/ChangeLog
index 851af24..2d0868c 100644
--- a/contrib/ChangeLog
+++ b/contrib/ChangeLog
@@ -1,3 +1,8 @@
+2001-07-26 Andreas Jaeger <aj@suse.de>,
+ Hans-Peter Nilsson <hp@bitrange.com>
+
+ * analyze_brprob: Fix documentation.
+
Mon Jul 23 15:47:19 CEST 2001 Jan Hubicka <jh@suse.cz>
* analyze_brprob: Fix awk compatibility problems; update comment.
@@ -40,7 +45,7 @@ Tue Jun 12 12:21:40 CEST 2001 Jan Hubicka <jh@suse.cz>
2001-06-11 Mark Mitchell <mark@codesourcery.com>
- * gcc_build: Output information about the commands used to
+ * gcc_build: Output information about the commands used to
configure the compiler.
2001-06-07 Joseph S. Myers <jsm28@cam.ac.uk>
diff --git a/contrib/analyze_brprob b/contrib/analyze_brprob
index c17f3d0..c385d84 100755
--- a/contrib/analyze_brprob
+++ b/contrib/analyze_brprob
@@ -22,7 +22,7 @@
#
#
# This script is used to calculate two basic properties of the branch prediction
-# heuristics - coverage and hitrate. Coverage is number of execution of a given
+# heuristics - coverage and hitrate. Coverage is number of executions of a given
# branch matched by the heuristics and hitrate is probability that once branch is
# predicted as taken it is really taken.
#
@@ -30,7 +30,7 @@
# may be directly used in predict.c.
#
# Usage:
-# Step 1: compile and profile your program. You need to use -fprofile-arcs
+# Step 1: Compile and profile your program. You need to use -fprofile-arcs
# flag to get the profiles
# Step 2: Generate log files. The information about given heuristics are
# saved into *.life dumps. You need to pass the -df switch to the compiler as well