diff options
| author | Andreas Jaeger <aj@suse.de> | 2001-07-23 10:39:58 +0000 |
|---|---|---|
| committer | Andreas Jaeger <aj@suse.de> | 2001-07-23 10:39:58 +0000 |
| commit | f2a2b6aef580068a5d6a5399b79c14a8bdf2431e (patch) | |
| tree | 3e88920994f7d8ededcbc7364bcd5489d3189170 /contrib | |
| parent | f132f4d4c95bcff2561e9340952083df725fbba2 (diff) | |
* analyze_brprob: Fix typos.
git-svn-id: https://gcc.gnu.org/svn/gcc/trunk@44262 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'contrib')
| -rw-r--r-- | contrib/ChangeLog | 4 | ||||
| -rwxr-xr-x | contrib/analyze_brprob | 6 |
2 files changed, 7 insertions, 3 deletions
diff --git a/contrib/ChangeLog b/contrib/ChangeLog index 7279ad9adcd..aa4d0bf0a7c 100644 --- a/contrib/ChangeLog +++ b/contrib/ChangeLog @@ -1,3 +1,7 @@ +2001-07-23 Andreas Jaeger <aj@suse.de> + + * analyze_brprob: Fix typos. + 2001-07-03 Joseph S. Myers <jsm28@cam.ac.uk> * texi2pod.pl: Handle @r inside @item. diff --git a/contrib/analyze_brprob b/contrib/analyze_brprob index 48068097d10..53de83e508f 100755 --- a/contrib/analyze_brprob +++ b/contrib/analyze_brprob @@ -1,5 +1,5 @@ #!/usr/bin/awk -f -# Script to analyze experimental results of our branch prediction heursitics +# Script to analyze experimental results of our branch prediction heuristics # Contributed by Jan Hubicka, SuSE inc. # Copyright (C) 2001 Free Software Foundation, Inc. # @@ -22,7 +22,7 @@ # # # This script is used to calculate two basic properties of the branch prediction -# heursitics - coverage and hitrate. Coverage is number of executions of given +# heuristics - coverage and hitrate. Coverage is number of executions of given # branch matched by the heuristics and hitrate is probability that once branch is # predicted as taken it is really taken. # @@ -58,7 +58,7 @@ #noreturn call 951 27.6% 100.00%/100.00% 1759809 17.6% # # The heuristics called "first match" is heuristics used by gcc branch -# prediction pass and it predicts 89.92% branches correctly. +# prediction pass and it predicts 89.92% branches correctly. # # The quality of heuristics can be rated using both, coverage and hitrate # parameters. For example "loop branch" heuristics (predicting loopback edge |