diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3bdbbe50845272cc342bcd5e12e1f751322efcce..66d15f84637abf4d3c9011647a86b27f02d2f80e 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,14 @@
+2003-10-05 Kazu Hirata <kazu@cs.umass.edu>
+
+ * 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.
+
2003-10-05 Kazu Hirata <kazu@cs.umass.edu>
* c-pretty-print.c: Fix comment formatting.
diff --git a/gcc/config/c4x/c4x.h b/gcc/config/c4x/c4x.h
index 1988ce6442ac4a6aa8791b3d16e2694806e0fa75..37d0c9b42dd471fb0e1d214f5ffcd4a82eda2bfd 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 0957fe9ef7062c7c0c139edacd05c290677efa83..5755177454a10dc1175a8d3a51c7f7ebde95c749 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 f934d8e2c9c12e27b031fb028857c9f3ef77fa53..ce5ce8bac25a8ddcc48216474fcfdb135a97c572 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 269a670b53de6902b9f257543395dc58769b7611..97897b88ca71963df7d76b19d8e04163cd34f227 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 cbe1864506693213a03d1a8483d4b8b0a6796fa8..4c1b878a011a6567a06544b6dc786c20e8573d97 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 86735f3364c0aa9ae942084184ca8124dbbb3332..68a2bd7663eba5dd29d0c45f5f2a59e9c0b9efe0 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
diff --git a/gcc/fold-const.c b/gcc/fold-const.c
index 1cf444d3f67f44d51f9f7b67a42a4a6bd7047912..92b885cc0c4e12e9f2186731d23452037d75394c 100644
--- a/gcc/fold-const.c
+++ b/gcc/fold-const.c
@@ -3098,7 +3098,7 @@ make_range (tree exp, int *pin_p, tree *plow, tree *phigh)
in_p = n_in_p, low = n_low, high = n_high;
- /* If the high bound is missing, but we have a non-zero low
+ /* If the high bound is missing, but we have a nonzero low
bound, reverse the range so it goes from zero to the low bound
minus 1. */
if (high == 0 && low && ! integer_zerop (low))
diff --git a/gcc/function.c b/gcc/function.c
index baec4ab3048a3c337a2e54a0583d022abd3eeb83..bd76c5cd1e10284d0dcded33da314a47b3db3d2f 100644
--- a/gcc/function.c
+++ b/gcc/function.c
@@ -4530,7 +4530,7 @@ assign_parms (tree fndecl)
Internally, gcc assumes that the argument pointer is
aligned to STACK_BOUNDARY bits. This is used both for
- alignment optimisations (see init_emit) and to locate
+ alignment optimizations (see init_emit) and to locate
arguments that are aligned to more than PARM_BOUNDARY
bits. We must preserve this invariant by rounding
CURRENT_FUNCTION_PRETEND_ARGS_SIZE up to a stack