This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFA: hook doc patch (27/112): TARGET_ASM_FUNCTION_EPILOGUE


Quoting Gerald Pfeifer <gerald@pfeifer.com>:
NACK.  We do not actually have current_function_pops_args any longer,
it was removed 2008-04-08.

Oops. Certainly a case where 'Take care of the sounds and the sense will take care of itself' doesn't work.

I assume you'll want to refer to incoming_args.pops_args instead?

Actually, it is crtl->args.pops_args.


2010-01-17  Joern Rennecke  <amylaar@spamcop.net>

	* tm.texi (TARGET_ASM_FUNCTION_EPILOGUE): Update text on where to
	find number of popped argument bytes.

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
+needs to know what was decided.  The number of bytes of the current
+function's arguments that this function should pop is available in
+@code{crtl->args.pops_args}.  @xref{Scalar Return}.
 @end deftypefn
 
 @itemize @bullet

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]