This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFA: hook doc patch (27/112): TARGET_ASM_FUNCTION_EPILOGUE
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Joern Rennecke <amylaar at spamcop dot net>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 16 Jan 2010 22:01:19 +0100 (CET)
- Subject: Re: RFA: hook doc patch (27/112): TARGET_ASM_FUNCTION_EPILOGUE
- References: <20100115124040.510c4x50u8ss08cc-nzlynne@webmail.spamcop.net>
On Fri, 15 Jan 2010, Joern Rennecke wrote:
2010-01-15 Joern Rennecke <amylaar@spamcop.net>
* tm.texi (TARGET_ASM_FUNCTION_EPILOGUE): Clarify the meaning of
'its'.
NACK. We do not actually have current_function_pops_args any longer,
it was removed 2008-04-08.
I assume you'll want to refer to incoming_args.pops_args instead?
Gerald
Index: tm.texi
===================================================================
--- tm.texi (revision 155367)
+++ tm.texi (working copy)
@@ -4698,10 +4720,8 @@ number of arguments.
Your definition of the macro @code{RETURN_POPS_ARGS} decides which
functions pop their own arguments. @code{TARGET_ASM_FUNCTION_EPILOGUE}
needs to know what was decided. The variable that is called
-@code{current_function_pops_args} is the number of bytes of its
-arguments that a function should pop. @xref{Scalar Return}.
-@c what is the "its arguments" in the above sentence referring to, pray
-@c tell? --mew 5feb93
+@code{current_function_pops_args} is the number of bytes of the current
+function's arguments that this function should pop. @xref{Scalar Return}.
@end deftypefn
@itemize @bullet