aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc/tm.texi
diff options
context:
space:
mode:
authorLars Brinkhoff <lars@nocrew.org>2001-08-03 01:19:20 +0000
committerJohn David Anglin <danglin@gcc.gnu.org>2001-08-03 01:19:20 +0000
commit8aeea6e67d77adc1a5e1575e4543d4259295be39 (patch)
tree84a4044443510c1b5b0e3a9c9f61f35ed627660b /gcc/doc/tm.texi
parent36e10d77f212d88ecc4f97fff8636cdb744c0cb9 (diff)
downloadgcc-8aeea6e67d77adc1a5e1575e4543d4259295be39.zip
gcc-8aeea6e67d77adc1a5e1575e4543d4259295be39.tar.gz
gcc-8aeea6e67d77adc1a5e1575e4543d4259295be39.tar.bz2
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
Diffstat (limited to 'gcc/doc/tm.texi')
-rw-r--r--gcc/doc/tm.texi6
1 files changed, 3 insertions, 3 deletions
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