diff options
author | Janis Johnson <janis187@us.ibm.com> | 2002-01-11 23:41:42 +0000 |
---|---|---|
committer | Janis Johnson <janis@gcc.gnu.org> | 2002-01-11 23:41:42 +0000 |
commit | aaef1c1262a37fdac4fa987b9b648f51c652521a (patch) | |
tree | f02a5b30af76c8a8f933b1128cf29fe6d72bacac | |
parent | 5d22c1a51893bd13a8cdc47dd635d2ed0e7646df (diff) | |
download | gcc-aaef1c1262a37fdac4fa987b9b648f51c652521a.zip gcc-aaef1c1262a37fdac4fa987b9b648f51c652521a.tar.gz gcc-aaef1c1262a37fdac4fa987b9b648f51c652521a.tar.bz2 |
* doc/rtl.texi (Insns): Fix 2 typos.
From-SVN: r48784
-rw-r--r-- | gcc/ChangeLog | 4 | ||||
-rw-r--r-- | gcc/doc/rtl.texi | 4 |
2 files changed, 6 insertions, 2 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e67d385..9331846 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2002-01-11 Janis Johnson <janis187@us.ibm.com> + + * doc/rtl.texi (Insns): Fix 2 typos. + 2002-01-11 Joseph S. Myers <jsm28@cam.ac.uk> * doc/invoke.texi: Avoid overfull hboxes. Add summary of D30V diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi index e2e2516..a50a9db 100644 --- a/gcc/doc/rtl.texi +++ b/gcc/doc/rtl.texi @@ -2681,7 +2681,7 @@ This means that the above invariants are not necessarily true for insns inside @code{sequence} expressions. Specifically, if @var{insn} is the first insn in a @code{sequence}, @code{NEXT_INSN (PREV_INSN (@var{insn}))} is the insn containing the @code{sequence} expression, as is the value -of @code{PREV_INSN (NEXT_INSN (@var{insn}))} is @var{insn} is the last +of @code{PREV_INSN (NEXT_INSN (@var{insn}))} if @var{insn} is the last insn in the @code{sequence} expression. You can use these expressions to find the containing @code{sequence} expression. @@ -3098,7 +3098,7 @@ insufficient registers are available. Except for stack homes for parameters, which are indicated by a @code{REG_EQUIV} note and are not useful to the early optimization passes and pseudo registers that are equivalent to a memory location -throughout there entire life, which is not detected until later in +throughout their entire life, which is not detected until later in the compilation, all equivalences are initially indicated by an attached @code{REG_EQUAL} note. In the early stages of register allocation, a @code{REG_EQUAL} note is changed into a @code{REG_EQUIV} note if |