Fix description of a stack element in a PARALLEL generated by FUNCTION_ARG

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@27096 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6440335..6db2126 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+Sat May 22 07:17:05 1999  Nick Clifton  <nickc@cygnus.com>
+
+       * tm.texi (FUNCTION_ARG): Correct description of a stack element
+       in a PARALLEL.
+
 Sat May 22 01:27:49 1999  Mark Mitchell  <mark@codesourcery.com>
 
        * expr.h (lang_expand_constant): Guard with #ifdef TREE_CODE.

diff --git a/gcc/tm.texi b/gcc/tm.texi
index 48f4439..d3bff3d 100644 (file)
--- a/gcc/tm.texi
+++ b/gcc/tm.texi
@@ -2794,9 +2794,8 @@ register RTX indicates how large this part of the argument is.  The
 second operand of the @code{expr_list} is a @code{const_int} which gives
 the offset in bytes into the entire argument of where this part starts.
 As a special exception the first @code{expr_list} in the @code{parallel} 
-RTX may have a first operand of zero.  This indicates that the bytes
-starting from the second operand of that @code{expr_list} are stored on
-the stack and not held in a register.
+RTX may have a first operand of zero.  This indicates that the entire
+argument is also stored on the stack.
 
 @cindex @file{stdarg.h} and register arguments
 The usual way to make the ANSI library @file{stdarg.h} work on a machine