summaryrefslogtreecommitdiff
path: root/gcc/predict.c
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2006-08-25 13:39:02 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2006-08-25 13:39:02 +0000
commitab4f0a13b12832be11af4fc129516f23cd7949be (patch)
tree946fc069d7c4945cd9418f4d8679df1cf39880fd /gcc/predict.c
parenta0a45ce87c4d8fa7acc55fcbd068a887bfb57e4a (diff)
downloadgcc-ab4f0a13b12832be11af4fc129516f23cd7949be.tar.gz
* doc/tm.texi: Fix a typo.
* predict.c: Fix comment typos. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@116399 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/predict.c')
-rw-r--r--gcc/predict.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/predict.c b/gcc/predict.c
index 3c2775cd69a..90307635dd8 100644
--- a/gcc/predict.c
+++ b/gcc/predict.c
@@ -182,7 +182,7 @@ tree_predicted_by_p (basic_block bb, enum br_predictor predictor)
The profile guessing code is good at predicting branch outcome (ie.
taken/not taken), that is predicted right slightly over 75% of time.
- It is however notorously poor on predicting the probability itself.
+ It is however notoriously poor on predicting the probability itself.
In general the profile appear a lot flatter (with probabilities closer
to 50%) than the reality so it is bad idea to use it to drive optimization
such as those disabling dynamic branch prediction for well predictable
@@ -192,7 +192,7 @@ tree_predicted_by_p (basic_block bb, enum br_predictor predictor)
predicted by number of iterations heuristics are predicted well. This macro
should be able to distinguish those, but at the moment it simply check for
noreturn heuristic that is only one giving probability over 99% or bellow
- 1%. In future we might want to propagate reliablity information across the
+ 1%. In future we might want to propagate reliability information across the
CFG if we find this information useful on multiple places. */
static bool
probability_reliable_p (int prob)