This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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] gas/*: Fix comment typos.


Hi,

Committed as obvious without a ChangeLog entry. (See
http://sources.redhat.com/ml/binutils/2003-10/msg00667.html.)

Kazu Hirata

Index: README-vms
===================================================================
RCS file: /cvs/src/src/gas/README-vms,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 README-vms
--- README-vms	3 May 1999 07:28:40 -0000	1.1.1.1
+++ README-vms	23 Nov 2003 02:10:12 -0000
@@ -150,7 +150,7 @@
 
 	5) If you are using the GNU-C++ compiler, you should modify the
 compiler driver file GNU_CC:[000000]GCC.COM (or GXX.COM).  If you have a
-seperate GXX.COM, then you need to change one line in GXX.COM to:
+separate GXX.COM, then you need to change one line in GXX.COM to:
 $ if f$locate("D",p2) .ne. P2_Length then Debug = " ""-G0"""
                                        Notice zero--->  ^
 If you are using a GCC.COM that does both C and C++, add the following lines to
@@ -196,7 +196,7 @@
 There are several *very* important differences, however.  First of all, since
 there is no function call involved, you cannot step over the inline function
 call - you always step into it. Secondly, since the same source lines are used
-in many locations, there is a seperate copy of the source for *each* usage. 
+in many locations, there is a separate copy of the source for *each* usage. 
 Without this, breakpoints do not work, since we must have a 1-to-1 mapping
 between source lines and PC.
 	Since you cannot step over inline function calls, it can be a real pain
Index: as.h
===================================================================
RCS file: /cvs/src/src/gas/as.h,v
retrieving revision 1.36
diff -u -r1.36 as.h
--- as.h	21 Nov 2003 01:52:16 -0000	1.36
+++ as.h	23 Nov 2003 02:10:12 -0000
@@ -301,7 +301,7 @@
 #endif
 typedef int subsegT;
 
-/* What subseg we are accreting now? */
+/* What subseg we are accessing now? */
 COMMON subsegT now_subseg;
 
 /* Segment our instructions emit to.  */
Index: dwarf2dbg.c
===================================================================
RCS file: /cvs/src/src/gas/dwarf2dbg.c,v
retrieving revision 1.65
diff -u -r1.65 dwarf2dbg.c
--- dwarf2dbg.c	21 Nov 2003 13:28:35 -0000	1.65
+++ dwarf2dbg.c	23 Nov 2003 02:10:13 -0000
@@ -247,7 +247,7 @@
   return ss;
 }
 
-/* Record an entry for LOC ocurring at OFS within the current fragment.  */
+/* Record an entry for LOC occurring at OFS within the current fragment.  */
 
 void
 dwarf2_gen_line_info (addressT ofs, struct dwarf2_line_info *loc)
Index: ecoff.c
===================================================================
RCS file: /cvs/src/src/gas/ecoff.c,v
retrieving revision 1.16
diff -u -r1.16 ecoff.c
--- ecoff.c	22 Nov 2003 00:20:48 -0000	1.16
+++ ecoff.c	23 Nov 2003 02:10:15 -0000
@@ -2863,7 +2863,7 @@
   else if (coff_symbol_typ == st_Member
 	   && coff_type.num_sizes - coff_type.extra_sizes == 1)
     {
-      /* Is this a bitfield?  This is indicated by a structure memeber
+      /* Is this a bitfield?  This is indicated by a structure member
          having a size field that isn't an array.  */
       coff_type.bitfield = 1;
     }
Index: hash.c
===================================================================
RCS file: /cvs/src/src/gas/hash.c,v
retrieving revision 1.10
diff -u -r1.10 hash.c
--- hash.c	27 Oct 2003 12:45:17 -0000	1.10
+++ hash.c	23 Nov 2003 02:10:15 -0000
@@ -23,7 +23,7 @@
 /* This version of the hash table code is a wholescale replacement of
    the old hash table code, which was fairly bad.  This is based on
    the hash table code in BFD, but optimized slightly for the
-   asssembler.  The assembler does not need to derive structures that
+   assembler.  The assembler does not need to derive structures that
    are stored in the hash table.  Instead, it always stores a pointer.
    The assembler uses the hash table mostly to store symbols, and we
    don't need to confuse the symbol structure with a hash table
Index: listing.c
===================================================================
RCS file: /cvs/src/src/gas/listing.c,v
retrieving revision 1.22
diff -u -r1.22 listing.c
--- listing.c	27 Oct 2003 12:45:17 -0000	1.22
+++ listing.c	23 Nov 2003 02:10:16 -0000
@@ -1,4 +1,4 @@
-/* listing.c - mainting assembly listings
+/* listing.c - maintain assembly listings
    Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
    2001, 2002
    Free Software Foundation, Inc.
Index: write.c
===================================================================
RCS file: /cvs/src/src/gas/write.c,v
retrieving revision 1.74
diff -u -r1.74 write.c
--- write.c	16 Aug 2003 13:35:08 -0000	1.74
+++ write.c	23 Nov 2003 02:10:17 -0000
@@ -1389,7 +1389,7 @@
 
 #ifndef SUB_SEGMENT_ALIGN
 #ifdef HANDLE_ALIGN
-/* The last subsegment gets an aligment corresponding to the alignment
+/* The last subsegment gets an alignment corresponding to the alignment
    of the section.  This allows proper nop-filling at the end of
    code-bearing sections.  */
 #define SUB_SEGMENT_ALIGN(SEG, FRCHAIN)					\


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