This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] cp: Fix comment typos.


Hi,

Committed as obvious.

Kazu Hirata

2004-03-11  Kazu Hirata  <kazu@cs.umass.edu>

	* call.c, cp-tree.h, pt.c: Fix comment typos.

Index: call.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/call.c,v
retrieving revision 1.467
diff -u -r1.467 call.c
--- call.c	9 Mar 2004 18:43:57 -0000	1.467
+++ call.c	11 Mar 2004 17:50:34 -0000
@@ -6470,7 +6470,7 @@
 	     itself the result of a function call), turn it into a
 	     TARGET_EXPR here.  It is important that EXPR be a
 	     TARGET_EXPR below since otherwise the INIT_EXPR will
-	     attempt to make a bitwise copy of EXPR to intialize
+	     attempt to make a bitwise copy of EXPR to initialize
 	     VAR. */
 	  if (TREE_CODE (expr) != TARGET_EXPR)
 	    expr = get_target_expr (expr);
Index: cp-tree.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/cp-tree.h,v
retrieving revision 1.956
diff -u -r1.956 cp-tree.h
--- cp-tree.h	9 Mar 2004 08:16:40 -0000	1.956
+++ cp-tree.h	11 Mar 2004 17:50:44 -0000
@@ -100,7 +100,7 @@
    4: DECL_C_BIT_FIELD (in a FIELD_DECL)
       DECL_VAR_MARKED_P (in a VAR_DECL)
       DECL_SELF_REFERENCE_P (in a TYPE_DECL)
-      DECL_INVALID_OVERRIRDER_P (in a FUNCTION_DECL)
+      DECL_INVALID_OVERRIDER_P (in a FUNCTION_DECL)
    5: DECL_INTERFACE_KNOWN.
    6: DECL_THIS_STATIC (in VAR_DECL or FUNCTION_DECL).
    7: DECL_DEAD_FOR_LOCAL (in VAR_DECL).
Index: pt.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/pt.c,v
retrieving revision 1.837
diff -u -r1.837 pt.c
--- pt.c	9 Mar 2004 15:35:00 -0000	1.837
+++ pt.c	11 Mar 2004 17:51:06 -0000
@@ -12131,7 +12131,7 @@
      There is at least one place where we want to know that a
      particular expression is a throw-expression: when checking a ?:
      expression, there are special rules if the second or third
-     argument is a throw-expresion.  */
+     argument is a throw-expression.  */
   if (TREE_CODE (expr) == THROW_EXPR)
     return expr;
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]