From c980b85bdc7dfa0fc6ffdc47bfef084441fcfb02 Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Sat, 22 May 1999 07:18:02 +0000 Subject: [PATCH] Fix description of a stack element in a PARALLEL generated by FUNCTION_ARG From-SVN: r27096 --- gcc/ChangeLog | 5 +++++ gcc/tm.texi | 5 ++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 64403354216..6db21265af9 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +Sat May 22 07:17:05 1999 Nick Clifton + + * tm.texi (FUNCTION_ARG): Correct description of a stack element + in a PARALLEL. + Sat May 22 01:27:49 1999 Mark Mitchell * expr.h (lang_expand_constant): Guard with #ifdef TREE_CODE. diff --git a/gcc/tm.texi b/gcc/tm.texi index 48f4439ed94..d3bff3df7a6 100644 --- 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 -- 2.30.2