diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 4cd2728a7d20b357a7db614762d7079be0f51609..0b3ee3438d648db2fd7d3341f305809b6fcfea8a 100644
--- 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 541ad4cea628ec9847c90a236e77858cb82b4f35..42c0c30683240a536e4bc3cf110c295200beec35 100644
--- 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 a5dc04960921e8f023e6e0d95133940e0f9e5f53..e72598d830ee1222c7b6e96ebdcde6abaf43639f 100644
--- 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