summaryrefslogtreecommitdiffstats
path: root/gcc/tm.texi
diff options
context:
space:
mode:
authorlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1998-02-19 00:04:36 +0000
committerlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1998-02-19 00:04:36 +0000
commitda2b9be0e0d38567f4997bb0a44fa99b40c18141 (patch)
treed0bc49ad3f508d937f5af8e2cd6dc3a36558dc27 /gcc/tm.texi
parentfbeaeaad2f8cebc22d556b5384d582dbdf94c1b7 (diff)
downloadppe42-gcc-da2b9be0e0d38567f4997bb0a44fa99b40c18141.tar.gz
ppe42-gcc-da2b9be0e0d38567f4997bb0a44fa99b40c18141.zip
Fix doc typos.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@18104 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/tm.texi')
-rw-r--r--gcc/tm.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/gcc/tm.texi b/gcc/tm.texi
index d4e6d4eecb1..168ee404db9 100644
--- a/gcc/tm.texi
+++ b/gcc/tm.texi
@@ -2314,7 +2314,7 @@ allocation has been done (for example, because the saved registers are
between these two locations). On those machines, define
@code{FRAME_POINTER_REGNUM} the number of a special, fixed register to
be used internally until the offset is known, and define
-@code{HARD_FRAME_POINTER_REGNUM} to be actual the hard register number
+@code{HARD_FRAME_POINTER_REGNUM} to be the actual hard register number
used for the frame pointer.
You should define this macro only in the very rare circumstances when it
@@ -5975,7 +5975,7 @@ operands to @code{asm_fprintf}.
Define the macros @code{REGISTER_PREFIX}, @code{LOCAL_LABEL_PREFIX},
@code{USER_LABEL_PREFIX} and @code{IMMEDIATE_PREFIX} if you can express
-the variations in assemble language syntax with that mechanism. Define
+the variations in assembly language syntax with that mechanism. Define
@code{ASSEMBLER_DIALECT} and use the @samp{@{option0|option1@}} syntax
if the syntax variant are larger and involve such things as different
opcodes or operand order.
@@ -6183,7 +6183,7 @@ expression of type @code{int}.
@findex ASM_NO_SKIP_IN_TEXT
@item ASM_NO_SKIP_IN_TEXT
Define this macro if @code{ASM_OUTPUT_SKIP} should not be used in the
-text section because it fails put zeros in the bytes that are skipped.
+text section because it fails to put zeros in the bytes that are skipped.
This is true on many Unix systems, where the pseudo--op to skip bytes
produces no-op instructions rather than zeros when used in the text
section.
@@ -6829,7 +6829,7 @@ incorrect definitions that omit an rtl code that may be matched by the
predicate can cause the compiler to malfunction). Instead, it allows
the table built by @file{genrecog} to be more compact and efficient,
thus speeding up the compiler. The most important predicates to include
-in the list specified by this macro are thoses used in the most insn
+in the list specified by this macro are those used in the most insn
patterns.
@findex CASE_VECTOR_MODE
OpenPOWER on IntegriCloud