This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] predict.c, doc/tm.texi: Fix typos.


Hi,

Committed as obvious.

Kazu Hirata

2006-08-25  Kazu Hirata  <kazu@codesourcery.com>

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

Index: doc/tm.texi
===================================================================
--- doc/tm.texi	(revision 116398)
+++ doc/tm.texi	(working copy)
@@ -4401,7 +4401,7 @@ compiler knows this regardless of @code{
 @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})
Index: predict.c
===================================================================
--- predict.c	(revision 116398)
+++ predict.c	(working copy)
@@ -182,7 +182,7 @@ tree_predicted_by_p (basic_block bb, enu
   
    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, enu
    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)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]