[Gc] [PATCH] remove doubled words from comments

[Jim Meyering]

This patch removes doubled words (here, they're all in comments),
making changes like s/to to/to/ and s/is is/is/, etc.

Affected files:

 configure.host               |    2 +-
 doc/README                   |    2 +-
 extra/setjmp_t.c             |    2 +-
 libatomic_ops/doc/README.txt |    2 +-
 os_dep.c                     |    4 ++--
 tests/huge_test.c            |    2 +-
 6 files changed, 7 insertions(+), 7 deletions(-)

To find candidates, I ran this command:
  vc-list-files | xargs perl -0777 -n \
  -e 'while (/\b(then?|[iao]n|i[fst]|but|f?or|at|and|[dt]o)\s+\1\b/gims)' \
  -e '{$n=($` =~ tr/\n/\n/ + 1); ($v=$&)=~s/\n/\\n/g; print "$ARGV:$n:$v\n"}'

where vc-list-files is from here:
  http://git.sv.gnu.org/cgit/gnulib.git/tree/build-aux/vc-list-files

Index: configure.host
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/configure.host,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 configure.host
--- configure.host	10 Oct 2005 22:33:34 -0000	1.1.1.1
+++ configure.host	11 Apr 2011 07:41:03 -0000
@@ -2,7 +2,7 @@
 
 # This shell script handles all host based configuration for the garbage
 # collector.
-# It sets various shell variables based on the the host and the
+# It sets various shell variables based on the host and the
 # configuration options.  You can modify this shell script without
 # needing to rerun autoconf.
 
Index: os_dep.c
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/os_dep.c,v
retrieving revision 1.107
diff -u -p -r1.107 os_dep.c
--- os_dep.c	10 Apr 2011 09:46:46 -0000	1.107
+++ os_dep.c	11 Apr 2011 07:41:12 -0000
@@ -2707,7 +2707,7 @@ STATIC void GC_default_push_other_roots(
         * the underlying memory was not allocated with the appropriate
         * flag.  This is common if GC_enable_incremental is called
         * shortly after GC initialization.  To avoid modifying the
-        * interface, we silently work around such a failure, it it only
+        * interface, we silently work around such a failure, it only
         * affects the initial (small) heap allocation.
         * If there are more dirty
         * pages than will fit in the buffer, this is not treated as a
@@ -4467,7 +4467,7 @@ GC_API int GC_CALL GC_get_pages_executab
 #    include <sys/frame.h>
 #  endif
 #  if NARGS > 6
-#    error We only know how to to get the first 6 arguments
+#    error We only know how to get the first 6 arguments
 #  endif
 #endif /* SPARC */
 
Index: doc/README
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/doc/README,v
retrieving revision 1.22
diff -u -p -r1.22 README
--- doc/README	27 Mar 2011 20:19:47 -0000	1.22
+++ doc/README	11 Apr 2011 07:41:14 -0000
@@ -129,7 +129,7 @@ ALL_INTERIOR_POINTERS defined, or GC_all
 set, as is now the default.
 
 Compiling without ALL_INTERIOR_POINTERS may reduce accidental retention
-of garbage objects, by requiring pointers from the heap to to the beginning
+of garbage objects, by requiring pointers from the heap to the beginning
 of an object.  But this no longer appears to be a significant
 issue for most programs occupying a small fraction of the possible
 address space.
Index: extra/setjmp_t.c
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/extra/setjmp_t.c,v
retrieving revision 1.1
diff -u -p -r1.1 setjmp_t.c
--- extra/setjmp_t.c	19 Sep 2009 11:43:14 -0000	1.1
+++ extra/setjmp_t.c	11 Apr 2011 07:41:14 -0000
@@ -16,7 +16,7 @@
 /* Compilers vary as to whether they will put x in a 	     */
 /* (callee-save) register without -O.  The code is	     */
 /* contrived such that any decent compiler should put x in   */
-/* a callee-save register with -O.  Thus it is is 	     */
+/* a callee-save register with -O.  Thus it is		     */
 /* recommended that this be run optimized.  (If the machine  */
 /* has no callee-save registers, then the generic code is    */
 /* safe, but this will not be noticed by this piece of       */
Index: libatomic_ops/doc/README.txt
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/libatomic_ops/doc/README.txt,v
retrieving revision 1.1
diff -u -p -r1.1 README.txt
--- libatomic_ops/doc/README.txt	29 Sep 2009 13:41:49 -0000	1.1
+++ libatomic_ops/doc/README.txt	11 Apr 2011 07:41:15 -0000
@@ -98,7 +98,7 @@ int compare_and_swap(volatile AO_t * add
         succeeded and *addr was updated.
 AO_TS_VAL_t test_and_set(volatile AO_TS_t * addr)
         Atomically read the binary value at *addr, and set it.  AO_TS_VAL_t
-        is an enumeration type which includes the two values AO_TS_SET and
+        is an enumeration type which includes the two values AO_TS_SET
         and AO_TS_CLEAR.  An AO_TS_t location is capable of holding an
         AO_TS_VAL_t, but may be much larger, as dictated by hardware
         constraints.  Test_and_set logically sets the value to AO_TS_SET.
Index: tests/huge_test.c
===================================================================
RCS file: /cvsroot/bdwgc/bdwgc/tests/huge_test.c,v
retrieving revision 1.2
diff -u -p -r1.2 huge_test.c
--- tests/huge_test.c	1 Oct 2009 19:23:14 -0000	1.2
+++ tests/huge_test.c	11 Apr 2011 07:41:16 -0000
@@ -14,7 +14,7 @@
 
 /*
  * Check that very large allocation requests fail.  "Success" would usually
- * indicate that the the size was somehow converted to a negative
+ * indicate that the size was somehow converted to a negative
  * number.  Clients shouldn't do this, but we should fail in the
  * expected manner.
  */