combine.c, [...]: consistently use "VAX", "VAXen", and "MicroVAX" in comments and documentation.

	* combine.c, config.gcc, cse.c, defaults.h, real.c, reload.c,
	simplify-rtx.c, config/alpha/alpha.h, config/avr/avr.h,
	config/convex/convex.h, config/d30v/d30v.c,
	config/d30v/d30v.h, config/dsp16xx/dsp16xx.h,
	config/elxsi/elxsi.h, config/fr30/fr30.h, config/m88k/m88k.c,
	config/mips/mips.h, config/mn10200/mn10200.h,
	config/mn10300/mn10300.h, config/pdp11/pdp11.md,
	config/v850/v850.h, config/vax/openbsd.h,
	config/vax/openbsd1.h, config/vax/ultrix.h,
	config/vax/vax-protos.h, config/vax/vax.c, config/vax/vax.h,
	config/vax/vax.md, config/vax/vaxv.h, config/vax/xm-vms.h,
	cp/decl2.c, doc/contrib.texi, doc/cpp.texi, doc/gcc.texi,
	doc/install.texi, doc/invoke.texi, doc/md.texi, doc/rtl.texi,
	doc/tm.texi: consistently use "VAX", "VAXen", and "MicroVAX"
        in comments and documentation.

From-SVN: r44589

8 files changed, 16 insertions, 16 deletions

diff --git a/gcc/doc/contrib.texi b/gcc/doc/contrib.texi
index 79f021d..caaf15b 100644
--- a/gcc/doc/contrib.texi
+++ b/gcc/doc/contrib.texi
@@ -540,7 +540,7 @@ Teemu Torma for thread safe exception handling support.
 
 @item
 Leonard Tower wrote parts of the parser, RTL generator, and RTL
-definitions, and of the Vax machine description.
+definitions, and of the VAX machine description.
 
 @item
 Tom Tromey for internationalization support and his Java work.
diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi
index 319f735..76d7b0c 100644
--- a/gcc/doc/cpp.texi
+++ b/gcc/doc/cpp.texi
@@ -2958,12 +2958,12 @@ are used as the error message.
 You would use @samp{#error} inside of a conditional that detects a
 combination of parameters which you know the program does not properly
 support.  For example, if you know that the program will not run
-properly on a Vax, you might write
+properly on a VAX, you might write
 
 @example
 @group
 #ifdef __vax__
-#error "Won't work on Vaxen.  See comments at get_last_object."
+#error "Won't work on VAXen.  See comments at get_last_object."
 #endif
 @end group
 @end example
diff --git a/gcc/doc/gcc.texi b/gcc/doc/gcc.texi
index 7bfc680..252f934 100644
--- a/gcc/doc/gcc.texi
+++ b/gcc/doc/gcc.texi
@@ -909,7 +909,7 @@ convention for structure and union returning.  Use the option
 @option{-mhc-struct-return} to tell GCC to use a convention compatible
 with it.
 
-@cindex Vax calling convention
+@cindex VAX calling convention
 @cindex Ultrix calling convention
 @item
 @opindex fcall-saved
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 902ac90..c0d7662 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3167,7 +3167,7 @@ On a System V release 4 system, make sure @file{/usr/bin} precedes
 <hr>
 @end html
 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
-Don't try compiling with Vax C (@code{vcc}).  It produces incorrect code
+Don't try compiling with VAX C (@code{vcc}).  It produces incorrect code
 in some cases (for example, when @code{alloca} is used).
 
 @html
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 7f1a79c..4ae2fc3 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -3263,14 +3263,14 @@ in many functions.  @strong{It also makes debugging impossible on
 some machines.}
 
 @ifset INTERNALS
-On some machines, such as the Vax, this flag has no effect, because
+On some machines, such as the VAX, this flag has no effect, because
 the standard calling sequence automatically handles the frame pointer
 and nothing is saved by pretending it doesn't exist.  The
 machine-description macro @code{FRAME_POINTER_REQUIRED} controls
 whether a target machine supports this flag.  @xref{Registers}.
 @end ifset
 @ifclear INTERNALS
-On some machines, such as the Vax, this flag has no effect, because
+On some machines, such as the VAX, this flag has no effect, because
 the standard calling sequence automatically handles the frame pointer
 and nothing is saved by pretending it doesn't exist.  The
 machine-description macro @code{FRAME_POINTER_REQUIRED} controls
@@ -5026,7 +5026,7 @@ command with the @option{-V} option.
 
 Earlier we discussed the standard option @option{-b} which chooses among
 different installed compilers for completely different target
-machines, such as Vax vs.@: 68000 vs.@: 80386.
+machines, such as VAX vs.@: 68000 vs.@: 80386.
 
 In addition, each of these target machine types can have its own
 special options, starting with @samp{-m}, to choose among various
@@ -5297,13 +5297,13 @@ The default is 4 for 68HC11 and 2 for 68HC12.
 @subsection VAX Options
 @cindex VAX options
 
-These @samp{-m} options are defined for the Vax:
+These @samp{-m} options are defined for the VAX:
 
 @table @gcctabopt
 @item -munix
 @opindex munix
 Do not output certain jump instructions (@code{aobleq} and so on)
-that the Unix assembler for the Vax cannot handle across long
+that the Unix assembler for the VAX cannot handle across long
 ranges.
 
 @item -mgnu
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index e546706..8fa221d 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -3131,7 +3131,7 @@ A comparison insn sets the condition code, recording the results of both
 signed and unsigned comparison of the given operands.  A separate branch
 insn tests the condition code and branches or not according its value.
 The branch insns come in distinct signed and unsigned flavors.  Many
-common machines, such as the Vax, the 68000 and the 32000, work this
+common machines, such as the VAX, the 68000 and the 32000, work this
 way.
 
 Some machines have distinct signed and unsigned compare instructions, and
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index e10c7b8..cfe7ba9 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -1620,7 +1620,7 @@ Represents the result of arithmetically shifting @var{x} left by @var{c}
 places.  @var{x} have mode @var{m}, a fixed-point machine mode.  @var{c}
 be a fixed-point mode or be a constant with mode @code{VOIDmode}; which
 mode is determined by the mode called for in the machine description
-entry for the left-shift instruction.  For example, on the Vax, the mode
+entry for the left-shift instruction.  For example, on the VAX, the mode
 of @var{c} is @code{QImode} regardless of @var{m}.
 
 @findex lshiftrt
@@ -2070,7 +2070,7 @@ valid for the mode of @var{lval}.
 @item (return)
 As the sole expression in a pattern, represents a return from the
 current function, on machines where this can be done with one
-instruction, such as Vaxes.  On machines where a multi-instruction
+instruction, such as VAXen.  On machines where a multi-instruction
 ``epilogue'' must be executed in order to return from the function,
 returning is done by jumping to a label which precedes the epilogue, and
 the @code{return} expression code is never used.
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index 34bea56..bdee2f8 100644
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -1304,7 +1304,7 @@ need to define this macro when the format is IEEE@.
 
 @findex VAX_FLOAT_FORMAT
 @item VAX_FLOAT_FORMAT
-This code indicates the peculiar format used on the Vax.
+This code indicates the peculiar format used on the VAX.
 
 @findex IBM_FLOAT_FORMAT
 @item IBM_FLOAT_FORMAT
@@ -3235,7 +3235,7 @@ in the compiler and was not mentioned in the C code being compiled.
 stack.  If a variable number of bytes is passed, it is zero, and
 argument popping will always be the responsibility of the calling function.
 
-On the Vax, all functions always pop their arguments, so the definition
+On the VAX, all functions always pop their arguments, so the definition
 of this macro is @var{stack-size}.  On the 68000, using the standard
 calling convention, no functions pop their arguments, so the value of
 the macro is always 0 in this case.  But an alternative calling
@@ -3274,7 +3274,7 @@ The value of the expression is usually either a @code{reg} RTX for the
 hard register in which to pass the argument, or zero to pass the
 argument on the stack.
 
-For machines like the Vax and 68000, where normally all arguments are
+For machines like the VAX and 68000, where normally all arguments are
 pushed, zero suffices as a definition.
 
 The value of the expression can also be a @code{parallel} RTX@.  This is