OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

tm.texi: Fix a typo. 

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

From-SVN: r116399
This commit is contained in:
Kazu Hirata 2006-08-25 13:39:02 +00:00 committed by Kazu Hirata
parent 17daa4c8ba
commit 86c33cd0fb
3 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -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

2
gcc/doc/tm.texi
View File

@ -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})

4
gcc/predict.c
View File

@ -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)