fold-const.c: Follow spelling conventions.

	* fold-const.c: Follow spelling conventions.
	* function.c: Likewise.
	* config/c4x/c4x.h: Likewise.
	* config/c4x/c4x.md: Likewise.
	* config/frv/frv.md: Likewise.
	* config/rs6000/aix.h: Likewise.
	* config/rs6000/linux64.h: Likewise.
	* config/xtensa/xtensa.c: Likewise.

From-SVN: r72111

6 files changed, 6 insertions, 6 deletions

diff --git a/gcc/config/c4x/c4x.h b/gcc/config/c4x/c4x.h
index 1988ce6..37d0c9b 100644
--- a/gcc/config/c4x/c4x.h
+++ b/gcc/config/c4x/c4x.h
@@ -777,7 +777,7 @@ enum reg_class
    the register arguments (R2,R3), respectively.  I'm reluctant to define
    this macro since it stomps on many potential optimizations.  Ideally
    it should have a register class argument so that not all the register
-   classes gets penalised for the sake of a naughty few...  For long
+   classes gets penalized for the sake of a naughty few...  For long
    double arithmetic we need two additional registers that we can use as
    spill registers.  */
 
diff --git a/gcc/config/c4x/c4x.md b/gcc/config/c4x/c4x.md
index 0957fe9..5755177 100644
--- a/gcc/config/c4x/c4x.md
+++ b/gcc/config/c4x/c4x.md
@@ -476,7 +476,7 @@
 ;
 ; C4x FUNCTIONAL UNITS
 ;
-; Define functional units for instruction scheduling to minimise
+; Define functional units for instruction scheduling to minimize
 ; pipeline conflicts.
 ;
 ; With the C3x, an external memory write (with no wait states) takes
diff --git a/gcc/config/frv/frv.md b/gcc/config/frv/frv.md
index f934d8e..ce5ce8ba 100644
--- a/gcc/config/frv/frv.md
+++ b/gcc/config/frv/frv.md
@@ -304,7 +304,7 @@
 
 ;; Instruction type
 
-;; The table below summarises the types of media instruction and their
+;; The table below summarizes the types of media instruction and their
 ;; scheduling classification.  Headings are:
 
 ;; Type:	the name of the define_attr type
diff --git a/gcc/config/rs6000/aix.h b/gcc/config/rs6000/aix.h
index 269a670..97897b8 100644
--- a/gcc/config/rs6000/aix.h
+++ b/gcc/config/rs6000/aix.h
@@ -155,7 +155,7 @@
    layout treating the parameter area as any other block of memory,
    then map the reg param area to registers, i.e., pad upward, which
    is the way IBM Compilers for AIX behave.
-   Setting both of the following defines results in this behaviour.  */
+   Setting both of the following defines results in this behavior.  */
 #define AGGREGATE_PADDING_FIXED 1
 #define AGGREGATES_PAD_UPWARD_ALWAYS 1
 
diff --git a/gcc/config/rs6000/linux64.h b/gcc/config/rs6000/linux64.h
index cbe1864..4c1b878a 100644
--- a/gcc/config/rs6000/linux64.h
+++ b/gcc/config/rs6000/linux64.h
@@ -241,7 +241,7 @@
    reasonably assume that they follow the normal rules for structure
    layout treating the parameter area as any other block of memory,
    then map the reg param area to registers.  ie. pad updard.
-   Setting both of the following defines results in this behaviour.
+   Setting both of the following defines results in this behavior.
    Setting just the first one will result in aggregates that fit in a
    doubleword being padded downward, and others being padded upward.
    Not a bad idea as this results in struct { int x; } being passed
diff --git a/gcc/config/xtensa/xtensa.c b/gcc/config/xtensa/xtensa.c
index 86735f3..68a2bd7 100644
--- a/gcc/config/xtensa/xtensa.c
+++ b/gcc/config/xtensa/xtensa.c
@@ -1724,7 +1724,7 @@ function_arg_advance (CUMULATIVE_ARGS *cum, enum machine_mode mode, tree type)
 
 
 /* Return an RTL expression containing the register for the given mode,
-   or 0 if the argument is to be passed on the stack.  INCOMING_P is non-zero
+   or 0 if the argument is to be passed on the stack.  INCOMING_P is nonzero
    if this is an incoming argument to the current function.  */
 
 rtx