public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [patch] tree-vectorizer.c: Fix comment typos.
@ 2005-03-30 15:38 Kazu Hirata
  0 siblings, 0 replies; only message in thread
From: Kazu Hirata @ 2005-03-30 15:38 UTC (permalink / raw)
  To: gcc-patches

Hi,

Committed as obvious.

Kazu Hirata

2005-03-30  Kazu Hirata  <kazu@cs.umass.edu>

	* tree-vectorizer.c: Fix comment typos.

Index: tree-vectorizer.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/tree-vectorizer.c,v
retrieving revision 2.82
diff -u -d -p -r2.82 tree-vectorizer.c
--- tree-vectorizer.c	29 Mar 2005 17:45:39 -0000	2.82
+++ tree-vectorizer.c	30 Mar 2005 15:18:57 -0000
@@ -807,11 +807,11 @@ slpeel_update_phi_nodes_for_guard2 (edge
 
       /* 3.1. Find the relevant names that need an exit-phi in GUARD_BB, i.e.
          names for which slpeel_update_phi_nodes_for_guard1 had not already
-         created a phi node. This is the case for names that are used out
-         side the loop (and therefore need an exit phi) but are not updated
+         created a phi node. This is the case for names that are used outside
+	 the loop (and therefore need an exit phi) but are not updated
          across loop iterations (and therefore don't have a loop-header-phi).
 
-         slpeel_update_phi_nodes_for_guard1 is responssible for creating
+         slpeel_update_phi_nodes_for_guard1 is responsible for creating
          loop-exit phis in GUARD_BB for names that have a loop-header-phi. When
          such a phi is created we also record the new name in SSA_NAME_AUX. If
          this new name exists, then guard_arg was set to this new name

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-03-30 15:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-30 15:38 [patch] tree-vectorizer.c: Fix comment typos Kazu Hirata

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).