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] config/m*: Fix comment typos.


Hi,

Attached is a patch to fix comment typos.  Committed as obvious.

Kazu Hirata

2003-07-03  Kazu Hirata  <kazu@cs.umass.edu>

	* config/m32r/m32r.c: Fix comment typos.
	* config/m68hc11/m68hc11.c: Likewise.
	* config/m68hc11/m68hc11.h: Likewise.
	* config/m68k/m68k.c: Likewise.
	* config/mcore/mcore.c: Likewise.
	* config/mcore/mcore.h: Likewise.
	* config/mcore/mcore.md: Likewise.
	* config/mips/mips.c: Likewise.
	* config/mips/mips.h: Likewise.
	* config/mips/mips.md: Likewise.
	* config/mips/netbsd.h: Likewise.
	* config/mn10300/mn10300.c: Likewise.

Index: config/m32r/m32r.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/m32r/m32r.c,v
retrieving revision 1.69
diff -u -r1.69 m32r.c
--- config/m32r/m32r.c	19 Jun 2003 21:47:14 -0000	1.69
+++ config/m32r/m32r.c	3 Jul 2003 12:27:06 -0000
@@ -1028,7 +1028,7 @@
 /* X and Y are two things to compare using CODE.  Emit the compare insn and
    return the rtx for compare [arg0 of the if_then_else].
    If need_compare is true then the comparison insn must be generated, rather
-   than being susummed into the following branch instruction.  */
+   than being subsumed into the following branch instruction.  */
 
 rtx
 gen_compare (code, x, y, need_compare)
@@ -1307,7 +1307,7 @@
 		ld r1,r3+; ld r2,r3
 
 	     if r3 were not used subsequently.  However, the REG_NOTES aren't
-	     propigated correctly by the reload phase, and it can cause bad
+	     propagated correctly by the reload phase, and it can cause bad
 	     code to be generated.  We could still try:
 
 		ld r1,r3+; ld r2,r3; addi r3,-4
@@ -1334,7 +1334,7 @@
 	st r1,r3; st r2,+r3
 
      if r3 were not used subsequently.  However, the REG_NOTES aren't
-     propigated correctly by the reload phase, and it can cause bad
+     propagated correctly by the reload phase, and it can cause bad
      code to be generated.  We could still try:
 
 	st r1,r3; st r2,+r3; addi r3,-4
@@ -1579,7 +1579,7 @@
       rtx * new_tail = new_head + (n_ready - 1);
       int   i;
 
-      /* Loop through the instructions, classifing them as short/long.  Try
+      /* Loop through the instructions, classifying them as short/long.  Try
 	 to keep 2 short together and/or 1 long.  Note, the ready list is
 	 actually ordered backwards, so keep it in that manner.  */
       for (i = n_ready-1; i >= 0; i--)
@@ -2586,7 +2586,7 @@
   if (mode != SImode && mode != HImode && mode != QImode)
     return FALSE;
 
-  /* At the moment we can hanndle moving registers and loading constants.  */
+  /* At the moment we can handle moving registers and loading constants.  */
   /* To be added: Addition/subtraction/bitops/multiplication of registers.  */
 
   switch (GET_CODE (operand))
@@ -2728,7 +2728,7 @@
 
 /* The maximum number of bytes to copy using pairs of load/store instructions.
    If a block is larger than this then a loop will be generated to copy
-   MAX_MOVE_BYTES chunks at a time.  The value of 32 is a semi-arbitary choice.
+   MAX_MOVE_BYTES chunks at a time.  The value of 32 is a semi-arbitrary choice.
    A customer uses Dhrystome as their benchmark, and Dhrystone has a 31 byte
    string copy in it.  */
 #define MAX_MOVE_BYTES 32
@@ -2788,7 +2788,7 @@
       /* If we are going to have to perform this loop more than
 	 once, then generate a label and compute the address the
 	 source register will contain upon completion of the final
-	 itteration.  */
+	 iteration.  */
       if (bytes > MAX_MOVE_BYTES)
 	{
 	  final_src = gen_reg_rtx (Pmode);
Index: config/m68hc11/m68hc11.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/m68hc11/m68hc11.c,v
retrieving revision 1.83
diff -u -r1.83 m68hc11.c
--- config/m68hc11/m68hc11.c	1 Jul 2003 01:15:05 -0000	1.83
+++ config/m68hc11/m68hc11.c	3 Jul 2003 12:27:07 -0000
@@ -2366,7 +2366,7 @@
 }
 
 /* Returns true if the operand 'op' must be printed with parenthesis
-   arround it.  This must be done only if there is a symbol whose name
+   around it.  This must be done only if there is a symbol whose name
    is a processor register.  */
 static int
 must_parenthesize (op)
@@ -4881,7 +4881,7 @@
 /* The insn uses the Z register.  Find a replacement register for it
    (either X or Y) and replace it in the insn and the next ones until
    the flow changes or the replacement register is used.  Instructions
-   are emited before and after the Z-block to preserve the value of
+   are emitted before and after the Z-block to preserve the value of
    Z and of the replacement register.  */
 
 static void
Index: config/m68hc11/m68hc11.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/m68hc11/m68hc11.h,v
retrieving revision 1.75
diff -u -r1.75 m68hc11.h
--- config/m68hc11/m68hc11.h	19 Jun 2003 21:47:15 -0000	1.75
+++ config/m68hc11/m68hc11.h	3 Jul 2003 12:27:08 -0000
@@ -1617,7 +1617,7 @@
 
 /* Assembler Commands for Exception Regions.  */
 
-/* Default values provided by GCC should be ok. Assumming that DWARF-2
+/* Default values provided by GCC should be ok. Assuming that DWARF-2
    frame unwind info is ok for this platform.  */
 
 #undef PREFERRED_DEBUGGING_TYPE
Index: config/m68k/m68k.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/m68k/m68k.c,v
retrieving revision 1.88
diff -u -r1.88 m68k.c
--- config/m68k/m68k.c	28 Jun 2003 00:36:23 -0000	1.88
+++ config/m68k/m68k.c	3 Jul 2003 12:27:10 -0000
@@ -3388,7 +3388,7 @@
 
 /* Operand predicates for implementing asymmetric pc-relative addressing
    on m68k.  The m68k supports pc-relative addressing (mode 7, register 2)
-   when used as a source operand, but not as a destintation operand.
+   when used as a source operand, but not as a destination operand.
 
    We model this by restricting the meaning of the basic predicates
    (general_operand, memory_operand, etc) to forbid the use of this
Index: config/mcore/mcore.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mcore/mcore.c,v
retrieving revision 1.47
diff -u -r1.47 mcore.c
--- config/mcore/mcore.c	16 May 2003 22:15:14 -0000	1.47
+++ config/mcore/mcore.c	3 Jul 2003 12:27:12 -0000
@@ -2370,7 +2370,7 @@
      registers during the prologue.  */
   number_of_regs_before_varargs = args_so_far + mcore_num_arg_regs (mode, type);
   
-  /* There is a bug somwehere in the arg handling code.
+  /* There is a bug somewhere in the arg handling code.
      Until I can find it this workaround always pushes the
      last named argument onto the stack.  */
   number_of_regs_before_varargs = args_so_far;
@@ -2586,7 +2586,7 @@
     }
 
   /* Give back anything else.  */
-  /* XXX: Should accumuate total and then give it back.  */
+  /* XXX: Should accumulate total and then give it back.  */
   while (growth >= 0)
     output_stack_adjust ( 1, fi.growth[growth--]);
 }
@@ -3147,7 +3147,7 @@
   if (type == NULL)
     return 0;
 
-  /* If the argugment can have its address taken, it must
+  /* If the argument can have its address taken, it must
      be placed on the stack.  */
   if (TREE_ADDRESSABLE (type))
     return 1;
@@ -3280,7 +3280,7 @@
 /* Implements the FUNCTION_ARG_PARTIAL_NREGS macro.
    Returns the number of argument registers required to hold *part* of
    a parameter of machine mode MODE and type TYPE (which may be NULL if
-   the type is not known).  If the argument fits entirly in the argument
+   the type is not known).  If the argument fits entirely in the argument
    registers, or entirely on the stack, then 0 is returned.  CUM is the
    number of argument registers already used by earlier parameters to
    the function.  */
Index: config/mcore/mcore.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mcore/mcore.h,v
retrieving revision 1.52
diff -u -r1.52 mcore.h
--- config/mcore/mcore.h	14 Jun 2003 21:47:42 -0000	1.52
+++ config/mcore/mcore.h	3 Jul 2003 12:27:13 -0000
@@ -258,7 +258,7 @@
 /* Allocation boundary (in *bits*) for storing arguments in argument list.  */
 #define PARM_BOUNDARY  	32
 
-/* Doubles must be alogned to an 8 byte boundary.  */
+/* Doubles must be aligned to an 8 byte boundary.  */
 #define FUNCTION_ARG_BOUNDARY(MODE, TYPE) \
   ((MODE != BLKmode && (GET_MODE_SIZE (MODE) == 8)) \
    ? BIGGEST_ALIGNMENT : PARM_BOUNDARY)
@@ -790,7 +790,7 @@
 /* Output assembler code for a block containing the constant parts
    of a trampoline, leaving space for the variable parts.
 
-   On the MCore, the trapoline looks like:
+   On the MCore, the trampoline looks like:
    	lrw	r1,  function
      	lrw	r13, area
    	jmp	r13
@@ -1195,7 +1195,7 @@
    games. This is because when we use this, we get a marked 
    reference through the call to assemble_name and this forces C++
    inlined member functions (or any inlined function) to be instantiated
-   regardless of whether any callsites remain.
+   regardless of whether any call sites remain.
    This makes this aspect of the compiler non-ABI compliant.  */
 
 /* Similar, but for libcall. FUN is an rtx.  */
Index: config/mcore/mcore.md
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mcore/mcore.md,v
retrieving revision 1.10
diff -u -r1.10 mcore.md
--- config/mcore/mcore.md	13 May 2003 18:41:27 -0000	1.10
+++ config/mcore/mcore.md	3 Jul 2003 12:27:14 -0000
@@ -691,7 +691,7 @@
 ;;
 ;; Other sizes may be handy for indexing. 
 ;; the tradeoffs to consider when adding these are
-;;	codesize, execution time [vs. mul it is easy to win],
+;;	code size, execution time [vs. mul it is easy to win],
 ;;	and register pressure -- these patterns don't use an extra
 ;;	register to build the offset from the base
 ;;	and whether the compiler will not come up with some other idiom.
Index: config/mips/mips.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mips/mips.c,v
retrieving revision 1.285
diff -u -r1.285 mips.c
--- config/mips/mips.c	2 Jul 2003 07:34:27 -0000	1.285
+++ config/mips/mips.c	3 Jul 2003 12:27:19 -0000
@@ -1141,7 +1141,7 @@
       return ADDRESS_INVALID;
 
     case CONST_INT:
-      /* Small-integer addressses don't occur very often, but they
+      /* Small-integer addresses don't occur very often, but they
 	 are legitimate if $0 is a valid base register.  */
       if (!TARGET_MIPS16 && SMALL_INT (x))
 	return ADDRESS_CONST_INT;
@@ -1591,7 +1591,7 @@
 }
 
 /* Return nonzero if the code is a relational operation suitable for a
-   conditional trap instructuion (only EQ, NE, LT, LTU, GE, GEU).
+   conditional trap instruction (only EQ, NE, LT, LTU, GE, GEU).
    We need this in the insn that expands `trap_if' in order to prevent
    combine from erroneously altering the condition.  */
 
@@ -3927,7 +3927,7 @@
 			|| TREE_CODE (type) == QUAL_UNION_TYPE));
 
   /* Decide whether this argument should go in a floating-point register,
-     assuming one is free.  Later code checks for availablity.  */
+     assuming one is free.  Later code checks for availability.  */
 
   info->fpr_p = false;
   if (GET_MODE_CLASS (mode) == MODE_FLOAT
@@ -7808,7 +7808,7 @@
     {
       /* For hosted applications, always put constants in small data if
 	 possible, as this gives the best performance.  */
-      /* ??? Consider using mergable small data sections.  */
+      /* ??? Consider using mergeable small data sections.  */
 
       if (GET_MODE_SIZE (mode) <= (unsigned) mips_section_threshold
 	  && mips_section_threshold > 0)
@@ -7985,18 +7985,18 @@
          There are three cases to consider:
 
             - o32 PIC (either with or without explicit relocs)
-            - n32/n64 PIC without explict relocs
+            - n32/n64 PIC without explicit relocs
             - n32/n64 PIC with explicit relocs
 
          In the first case, both local and global accesses will use an
          R_MIPS_GOT16 relocation.  We must correctly predict which of
          the two semantics (local or global) the assembler and linker
          will apply.  The choice doesn't depend on the symbol's
-         visibility, so we deliberately ignore decl_visiblity and
+         visibility, so we deliberately ignore decl_visibility and
          binds_local_p here.
 
          In the second case, the assembler will not use R_MIPS_GOT16
-         relocations, but it chooses between local and global accessees
+         relocations, but it chooses between local and global accesses
          in the same way as for o32 PIC.
 
          In the third case we have more freedom since both forms of
@@ -8519,7 +8519,7 @@
 }
 
 /* Build a mips16 function stub.  This is used for functions which
-   take aruments in the floating point registers.  It is 32 bit code
+   take arguments in the floating point registers.  It is 32 bit code
    that moves the floating point args into the general registers, and
    then jumps to the 16 bit code.  */
 
Index: config/mips/mips.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mips/mips.h,v
retrieving revision 1.270
diff -u -r1.270 mips.h
--- config/mips/mips.h	2 Jul 2003 00:21:56 -0000	1.270
+++ config/mips/mips.h	3 Jul 2003 12:27:21 -0000
@@ -1622,7 +1622,7 @@
    done, NIL if none.
 
    When in 64 bit mode, mips_move_1word will sign extend SImode and CCmode
-   moves.  All other referces are zero extended.  */
+   moves.  All other references are zero extended.  */
 #define LOAD_EXTEND_OP(MODE) \
   (TARGET_64BIT && ((MODE) == SImode || (MODE) == CCmode) \
    ? SIGN_EXTEND : ZERO_EXTEND)
@@ -1732,7 +1732,7 @@
    all the FIXED_REGISTERS.  Until this problem has been
    resolved this macro can be used to overcome this situation.
    In particular, block_propagate() requires this list
-   be acurate, or we can remove registers which should be live.
+   be accurate, or we can remove registers which should be live.
    This macro is used in regs_invalidated_by_call.  */
 
 
@@ -2382,7 +2382,7 @@
 /* The return address for the current frame is in r31 if this is a leaf
    function.  Otherwise, it is on the stack.  It is at a variable offset
    from sp/fp/ap, so we define a fake hard register rap which is a
-   poiner to the return address on the stack.  This always gets eliminated
+   pointer to the return address on the stack.  This always gets eliminated
    during reload to be either the frame pointer or the stack pointer plus
    an offset.  */
 
Index: config/mips/mips.md
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mips/mips.md,v
retrieving revision 1.179
diff -u -r1.179 mips.md
--- config/mips/mips.md	2 Jul 2003 07:36:04 -0000	1.179
+++ config/mips/mips.md	3 Jul 2003 12:27:23 -0000
@@ -8819,7 +8819,7 @@
 
 ;; call_insn_operand will only accepts constant addresses if a direct
 ;; jump is acceptable.  Since the 'S' constraint is defined in terms of
-;; call_insn_operand, the same is true of the contraints.
+;; call_insn_operand, the same is true of the constraints.
 
 ;; When we use an indirect jump, we need a register that will be
 ;; preserved by the epilogue.  Since TARGET_ABICALLS forces us to
Index: config/mips/netbsd.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mips/netbsd.h,v
retrieving revision 1.28
diff -u -r1.28 netbsd.h
--- config/mips/netbsd.h	8 Jan 2003 19:57:50 -0000	1.28
+++ config/mips/netbsd.h	3 Jul 2003 12:27:24 -0000
@@ -58,7 +58,7 @@
    them here.  Note this is structured for easy comparison to the version
    in mips.h.
 
-   FIXME: This probably isn't the best solution.  But in the absense
+   FIXME: This probably isn't the best solution.  But in the absence
    of something better, it will have to do, for now.  */
 
 #undef TARGET_CPU_CPP_BUILTINS
Index: config/mn10300/mn10300.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mn10300/mn10300.c,v
retrieving revision 1.51
diff -u -r1.51 mn10300.c
--- config/mn10300/mn10300.c	19 Jun 2003 21:47:18 -0000	1.51
+++ config/mn10300/mn10300.c	3 Jul 2003 12:27:24 -0000
@@ -581,7 +581,7 @@
      Else leave it alone, it will be cut back as part of the
      ret/retf instruction, or there wasn't any stack to begin with.
 
-     Under no circumstanes should the register save area be
+     Under no circumstances should the register save area be
      deallocated here, that would leave a window where an interrupt
      could occur and trash the register save area.  */
   if (frame_pointer_needed)


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