Commit 66a4ad37 by Kazu Hirata Committed by Kazu Hirata

op-common.h, [...]: Fix comment typos.

	* config/soft-fp/op-common.h, double-int.h, tree-ssa-dom.c:
	Fix comment typos.
	* doc/tm.texi: Fix a typo.

From-SVN: r113178
parent 9f9a713e
2006-04-22 Kazu Hirata <kazu@codesourcery.com>
* config/soft-fp/op-common.h, double-int.h, tree-ssa-dom.c:
Fix comment typos.
* doc/tm.texi: Fix a typo.
2006-04-21 Geoffrey Keating <geoffk@apple.com> 2006-04-21 Geoffrey Keating <geoffk@apple.com>
* dwarf2out.c (struct die_struct): Document that die_sib makes * dwarf2out.c (struct die_struct): Document that die_sib makes
......
...@@ -35,7 +35,7 @@ ...@@ -35,7 +35,7 @@
_FP_FRAC_DECL_##wc(X) _FP_FRAC_DECL_##wc(X)
/* /*
* Finish truely unpacking a native fp value by classifying the kind * Finish truly unpacking a native fp value by classifying the kind
* of fp value and normalizing both the exponent and the fraction. * of fp value and normalizing both the exponent and the fraction.
*/ */
......
...@@ -9144,7 +9144,7 @@ such cases may improve things. ...@@ -9144,7 +9144,7 @@ such cases may improve things.
@end defmac @end defmac
@deftypefn {Target Hook} int TARGET_MODE_REP_EXTENDED (enum machine_mode @var{mode}, enum machine_mode @var{rep_mode}) @deftypefn {Target Hook} int TARGET_MODE_REP_EXTENDED (enum machine_mode @var{mode}, enum machine_mode @var{rep_mode})
The representation of an intergral mode can be such that the values The representation of an integral mode can be such that the values
are always extended to a wider integral mode. Return are always extended to a wider integral mode. Return
@code{SIGN_EXTEND} if values of @var{mode} are represented in @code{SIGN_EXTEND} if values of @var{mode} are represented in
sign-extended form to @var{rep_mode}. Return @code{UNKNOWN} sign-extended form to @var{rep_mode}. Return @code{UNKNOWN}
......
...@@ -44,7 +44,7 @@ Software Foundation, 51 Franklin Street, Fifth Floor, Boston, MA ...@@ -44,7 +44,7 @@ Software Foundation, 51 Franklin Street, Fifth Floor, Boston, MA
??? The components of double_int differ in signedness mostly for ??? The components of double_int differ in signedness mostly for
historical reasons (they replace an older structure used to represent historical reasons (they replace an older structure used to represent
numbers with precision wigher than HOST_WIDE_INT). It might be less numbers with precision higher than HOST_WIDE_INT). It might be less
confusing to have them both signed or both unsigned. */ confusing to have them both signed or both unsigned. */
typedef struct typedef struct
......
...@@ -2439,7 +2439,7 @@ eliminate_degenerate_phis (void) ...@@ -2439,7 +2439,7 @@ eliminate_degenerate_phis (void)
A set bit indicates that the statement or PHI node which A set bit indicates that the statement or PHI node which
defines the SSA_NAME should be (re)examined to determine if defines the SSA_NAME should be (re)examined to determine if
it has become a degenerate PHI or trival const/copy propagation it has become a degenerate PHI or trivial const/copy propagation
opportunity. opportunity.
Experiments have show we generally get better compilation Experiments have show we generally get better compilation
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment