This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RFA: hook signture patches (10/11): TARGET_RETURN_POPS_ARGS
- From: Joern Rennecke <amylaar at spamcop dot net>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 29 Jun 2010 22:09:02 -0400
- Subject: RFA: hook signture patches (10/11): TARGET_RETURN_POPS_ARGS
2010-06-29 Joern Rennecke <joern.rennecke@embecosm.com>
* target.def (return_pops_args): Use DEFHOOK.
* doc/tm.texi.in (TARGET_RETURN_POPS_ARGS): Use @hook.
Rename stack-size to size.
* doc/tm.texi: Regenerate.
Index: doc/tm.texi
===================================================================
--- doc/tm.texi (revision 161563)
+++ doc/tm.texi (working copy)
@@ -3931,7 +3931,7 @@ suppresses this behavior and causes the
stack in its natural location.
@end defmac
-@deftypefn {Target Hook} TARGET_RETURN_POPS_ARGS (@var{fundecl}, @var{funtype}, @var{stack-size})
+@deftypefn {Target Hook} int TARGET_RETURN_POPS_ARGS (tree @var{fundecl}, tree @var{funtype}, int @var{size})
This target hook returns the number of bytes of its own arguments that
a function pops on returning, or 0 if the function pops no arguments
and the caller must therefore pop them all after the function returns.
@@ -3954,12 +3954,12 @@ by their names. Note that ``library fun
a function used to perform arithmetic, whose name is known specially
in the compiler and was not mentioned in the C code being compiled.
-@var{stack-size} is the number of bytes of arguments passed on the
+@var{size} is the number of bytes of arguments passed on the
stack. If a variable number of bytes is passed, it is zero, and
argument popping will always be the responsibility of the calling function.
On the VAX, all functions always pop their arguments, so the definition
-of this macro is @var{stack-size}. On the 68000, using the standard
+of this macro is @var{size}. On the 68000, using the standard
calling convention, no functions pop their arguments, so the value of
the macro is always 0 in this case. But an alternative calling
convention is available in which functions that take a fixed number of
Index: doc/tm.texi.in
===================================================================
--- doc/tm.texi.in (revision 161563)
+++ doc/tm.texi.in (working copy)
@@ -3931,7 +3931,7 @@ suppresses this behavior and causes the
stack in its natural location.
@end defmac
-@deftypefn {Target Hook} TARGET_RETURN_POPS_ARGS (@var{fundecl}, @var{funtype}, @var{stack-size})
+@hook TARGET_RETURN_POPS_ARGS
This target hook returns the number of bytes of its own arguments that
a function pops on returning, or 0 if the function pops no arguments
and the caller must therefore pop them all after the function returns.
@@ -3954,12 +3954,12 @@ by their names. Note that ``library fun
a function used to perform arithmetic, whose name is known specially
in the compiler and was not mentioned in the C code being compiled.
-@var{stack-size} is the number of bytes of arguments passed on the
+@var{size} is the number of bytes of arguments passed on the
stack. If a variable number of bytes is passed, it is zero, and
argument popping will always be the responsibility of the calling function.
On the VAX, all functions always pop their arguments, so the definition
-of this macro is @var{stack-size}. On the 68000, using the standard
+of this macro is @var{size}. On the 68000, using the standard
calling convention, no functions pop their arguments, so the value of
the macro is always 0 in this case. But an alternative calling
convention is available in which functions that take a fixed number of
Index: target.def
===================================================================
--- target.def (revision 161563)
+++ target.def (working copy)
@@ -1873,7 +1861,7 @@ DEFHOOK
pops on returning, or 0 if the function pops no arguments and the
caller must therefore pop them all after the function returns. */
/* ??? tm.texi has no types for the parameters. */
-DEFHOOK_UNDOC
+DEFHOOK
(return_pops_args,
"",
int, (tree fundecl, tree funtype, int size),