PR tree-optimization/21170

	* tree-ssa-dom.c, tree-ssa-threadupdate.c: Replace
	rewrite_ssa_into_ssa in comments with update_ssa.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@99540 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 4cd2728..0b3ee34 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2005-05-10  Kazu Hirata  <kazu@cs.umass.edu>
+
+       PR tree-optimization/21170
+       * tree-ssa-dom.c, tree-ssa-threadupdate.c: Replace
+       rewrite_ssa_into_ssa in comments with update_ssa.
+
 2005-05-10  Zdenek Dvorak  <dvorakz@suse.cz>
 
        * tree-ssa-loop-im.c: Include hashtab.h.

diff --git a/gcc/tree-ssa-dom.c b/gcc/tree-ssa-dom.c
index 541ad4c..42c0c30 100644 (file)
--- a/gcc/tree-ssa-dom.c
+++ b/gcc/tree-ssa-dom.c
@@ -486,7 +486,7 @@ tree_ssa_dominator_optimize (void)
 
         This must be done before we iterate as we might have a
         reference to an SSA_NAME which was removed by the call to
-        rewrite_ssa_into_ssa.
+        update_ssa.
 
         Long term we will be able to let everything in SSA_NAME_VALUE
         persist.  However, for now, we know this is the safe thing to do.  */

diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c
index a5dc049..e72598d 100644 (file)
--- a/gcc/tree-ssa-threadupdate.c
+++ b/gcc/tree-ssa-threadupdate.c
@@ -648,8 +648,8 @@ redirect_edges (void **slot, void *data)
    the appropriate duplicate of BB.
 
    BB and its duplicates will have assignments to the same set of
-   SSA_NAMEs.  Right now, we just call into rewrite_ssa_into_ssa
-   to update the SSA graph for those names.
+   SSA_NAMEs.  Right now, we just call into update_ssa to update the
+   SSA graph for those names.
 
    We are also going to experiment with a true incremental update
    scheme for the duplicated resources.  One of the interesting