tm.texi: Fix a typo.

	* doc/tm.texi: Fix a typo.
	* predict.c: Fix comment typos.

From-SVN: r116399

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index fa159a14329d8f559780816565ea68fe5edfa599..e5f5ff7f77ae7978068855d1b94ff25ef51d68f9 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2006-08-25  Kazu Hirata  <kazu@codesourcery.com>
+
+       * doc/tm.texi: Fix a typo.
+       * predict.c: Fix comment typos.
+
 2006-08-25  Nick Clifton  <nickc@redhat.com>
 
        * config/mn10300/mn10300.h (TARGET_CPU_CPP_BUILTINS): Add

diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index 29c1ce2b90e67acb60d425cbd724d88e0d4670af..32f00052df1465a4a238c7d7c0ef98b0c38ded1b 100644 (file)
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -4401,7 +4401,7 @@ compiler knows this regardless of @code{EXIT_IGNORE_STACK}.
 @defmac EPILOGUE_USES (@var{regno})
 Define this macro as a C expression that is nonzero for registers that are
 used by the epilogue or the @samp{return} pattern.  The stack and frame
-pointer registers are already be assumed to be used as needed.
+pointer registers are already assumed to be used as needed.
 @end defmac
 
 @defmac EH_USES (@var{regno})

diff --git a/gcc/predict.c b/gcc/predict.c
index 3c2775cd69a67476f2ea5ac55026e4e055ac69d0..90307635dd87859a59daa40b204e35979dcf763a 100644 (file)
--- 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)