Commit 68e82b83 by Kazu Hirata Committed by Kazu Hirata

fold-const.c: Fix comment typos.

	* fold-const.c: Fix comment typos.
	* gcse.c: Likewise.
	* reload1.c: Likewise.

From-SVN: r55876
parent fe6b547a
2002-07-30 Kazu Hirata <kazu@cs.umass.edu>
* fold-const.c: Fix comment typos.
* gcse.c: Likewise.
* reload1.c: Likewise.
2002-07-29 Aldy Hernandez <aldyh@redhat.com> 2002-07-29 Aldy Hernandez <aldyh@redhat.com>
* config/rs6000/rs6000.md: Disallow CCEQ compare with crnor/crnot * config/rs6000/rs6000.md: Disallow CCEQ compare with crnor/crnot
......
...@@ -2716,7 +2716,7 @@ sign_bit_p (exp, val) ...@@ -2716,7 +2716,7 @@ sign_bit_p (exp, val)
int width; int width;
tree t; tree t;
/* Tree EXP must have a integral type. */ /* Tree EXP must have an integral type. */
t = TREE_TYPE (exp); t = TREE_TYPE (exp);
if (! INTEGRAL_TYPE_P (t)) if (! INTEGRAL_TYPE_P (t))
return NULL_TREE; return NULL_TREE;
......
...@@ -5850,7 +5850,7 @@ static sbitmap *hoist_exprs; ...@@ -5850,7 +5850,7 @@ static sbitmap *hoist_exprs;
dominance_info dominators; dominance_info dominators;
/* ??? We could compute post dominators and run this algorithm in /* ??? We could compute post dominators and run this algorithm in
reverse to to perform tail merging, doing so would probably be reverse to perform tail merging, doing so would probably be
more effective than the tail merging code in jump.c. more effective than the tail merging code in jump.c.
It's unclear if tail merging could be run in parallel with It's unclear if tail merging could be run in parallel with
......
...@@ -4321,7 +4321,7 @@ clear_reload_reg_in_use (regno, opnum, type, mode) ...@@ -4321,7 +4321,7 @@ clear_reload_reg_in_use (regno, opnum, type, mode)
abort (); abort ();
} }
/* We resolve conflicts with remaining reloads of the same type by /* We resolve conflicts with remaining reloads of the same type by
excluding the intervals of of reload registers by them from the excluding the intervals of reload registers by them from the
interval of freed reload registers. Since we only keep track of interval of freed reload registers. Since we only keep track of
one set of interval bounds, we might have to exclude somewhat one set of interval bounds, we might have to exclude somewhat
more than what would be necessary if we used a HARD_REG_SET here. more than what would be necessary if we used a HARD_REG_SET here.
......
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