install.texi: Follow spelling conventions.

	* doc/install.texi: Follow spelling conventions.
	* doc/tm.texi: Likewise.
	* config/fp-bit.c: Likewise.
	* config/arm/arm.c: Likewise.
	* config/frv/frv.c: Likewise.
	* config/ns32k/NOTES: Likewise.
	* config/ns32k/STATUS: Likewise.

From-SVN: r67962

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 15030b1aa9b7ad1ed8ff7b0f7f25f7552335e2ee..d38c768a40923479c06360fe63a844359f4da945 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2003-06-14  Kazu Hirata  <kazu@cs.umass.edu>
+
+       * doc/install.texi: Follow spelling conventions.
+       * doc/tm.texi: Likewise.
+       * config/fp-bit.c: Likewise.
+       * config/arm/arm.c: Likewise.
+       * config/frv/frv.c: Likewise.
+       * config/ns32k/NOTES: Likewise.
+       * config/ns32k/STATUS: Likewise.
+
 2003-06-14  Roger Sayle  <roger@eyesopen.com>
            Zack Weinberg  <zack@codesourcery.com>
 

diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index 23500feeaa8013b3915ace2f1a8e11a77c848419..4a42f0b998e38611258da66924c0fec35a01dcc8 100644 (file)
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -2350,7 +2350,7 @@ arm_function_ok_for_sibcall (tree decl, tree exp ATTRIBUTE_UNUSED)
 \f
 /* Addressing mode support functions.  */
 
-/* Return non-zero if X is a legitimate immediate operand when compiling
+/* Return nonzero if X is a legitimate immediate operand when compiling
    for PIC.  */
 int
 legitimate_pic_operand_p (rtx x)

diff --git a/gcc/config/fp-bit.c b/gcc/config/fp-bit.c
index b8ac2982cdd734573e2b99f29a0f90e064d18d51..6640f7ad1b4ebeef6ddd09515b837d087414c576 100644 (file)
--- a/gcc/config/fp-bit.c
+++ b/gcc/config/fp-bit.c
@@ -371,7 +371,7 @@ pack_d ( fp_number_type *  src)
               if (low >= ((halffractype)1 << HALFFRACBITS))
                 /* We don't shift left, since it has just become the
                    smallest normal number, whose implicit 1 bit is
-                   now indicated by the non-zero exponent.  */
+                   now indicated by the nonzero exponent.  */
                 exp++;
             }
         }

diff --git a/gcc/config/frv/frv.c b/gcc/config/frv/frv.c
index c2a8ef95c6cdc5e5c9b8d2e9f6507a7e8a325d66..e6640875054a80609eadad7932db3285cfc7a5f3 100644 (file)
--- a/gcc/config/frv/frv.c
+++ b/gcc/config/frv/frv.c
@@ -2338,8 +2338,8 @@ frv_final_prescan_insn (insn, opvec, noperands)
 
      Printable instructions will be asm_operands or match one of the .md
      patterns.  Since asm instructions cannot be packed -- and will
-     therefore have TImode -- this loop terminates on any recognisable
-     instruction, and on any unrecognisable instruction with TImode.  */
+     therefore have TImode -- this loop terminates on any recognizable
+     instruction, and on any unrecognizable instruction with TImode.  */
   for (insn = NEXT_INSN (insn); insn; insn = NEXT_INSN (insn))
     {
       if (NOTE_P (insn))

diff --git a/gcc/config/ns32k/NOTES b/gcc/config/ns32k/NOTES
index 46882461d0292d4cbb8d0e57f8be08a864c054f7..824c80c841e73ff4307e2e66c61e26dd004ca856 100644 (file)
--- a/gcc/config/ns32k/NOTES
+++ b/gcc/config/ns32k/NOTES
@@ -10,7 +10,7 @@ Ian Dall <ian@beware.dropbear.id.au>
 ------------------------------------
 
 The ns32x81 fpu handles most operands in hardware, but traps on NaN,
-Inf and Denormalized numbers. The correct behaviour can be handled by
+Inf and Denormalized numbers. The correct behavior can be handled by
 the trap handler. This is mostly transparent to the compiler, but in
 the case of floating point comparisions, the trap handler and the
 compiler must co-operate.

diff --git a/gcc/config/ns32k/STATUS b/gcc/config/ns32k/STATUS
index 2754bf1f07a34f102397a1695ae4162c1300d296..546725580139914269b103b099328b2f19515ff5 100644 (file)
--- a/gcc/config/ns32k/STATUS
+++ b/gcc/config/ns32k/STATUS
@@ -28,7 +28,7 @@ correct if not ideal.
 gcc.dg/debug/debug-1.c scan-assembler xyzzy:
 At -O3 level of optimization, variable xyzzy gets eliminated. Isn't it
 reasonable that the debugging info is gone too? Indeed, the
-documentation says this is expected behaviour.
+documentation says this is expected behavior.
 
 gcc.dg/debug/debug-2.c scan-assembler xyzzy:
 As for the above.
@@ -61,7 +61,7 @@ gcc.dg/uninit-A.c -O2 -Wall -S
 Bogus warnings, almost certainly not backend.
 
 gcc.dg/special/weak-1.c execution test
-X  This fails for i386 too. I don't understand what the correct behaviour
+X  This fails for i386 too. I don't understand what the correct behavior
 for this test is.
 
 gcc.dg/special/gcsec-1.c (test for excess errors)

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 7c82d0b4a53884602196705bde2ab347792448fe..546a968fd7b87f224ca9938adfb4ac3fe7f5ed48 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2557,7 +2557,7 @@ OpenServer, you must have at least the first maintenance pack installed
 the "Execution Environment Update", provides updated link editors and
 assemblers, as well as updated standard C and math libraries.  The C
 startup modules are also updated to support the System V gABI draft, and
-GCC relies on that behaviour.  OSS631 provides a collection of commonly
+GCC relies on that behavior.  OSS631 provides a collection of commonly
 used open source libraries, some of which GCC depends on (such as GNU
 gettext and zlib).  SCO OpenServer Release 5.0.7 has all of this built
 in by default, but OSS631C and later also apply to that release.  Please

diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index 24775b2837c9cae868b163b551081943a6910330..b83781642cb2c00cd162f7452674ad7ed2b1227b 100644 (file)
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -2840,9 +2840,9 @@ value @code{STARTING_FRAME_OFFSET}.
 @findex STACK_ALIGNMENT_NEEDED
 @item STACK_ALIGNMENT_NEEDED
 Define to zero to disable final alignment of the stack during reload.
-The non-zero default for this macro is suitable for most ports.
+The nonzero default for this macro is suitable for most ports.
 
-On ports where @code{STARTING_FRAME_OFFSET} is non-zero or where there
+On ports where @code{STARTING_FRAME_OFFSET} is nonzero or where there
 is a register save block following the local block that doesn't require
 alignment to @code{STACK_BOUNDARY}, it may be beneficial to disable
 stack alignment and do it in the backend.