This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] tm.texi: Replace SETUP_INCOMING_VARARGS withTARGET_SETUP_INCOMING_VARARGS.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc-patches at gcc dot gnu dot org
- Date: Wed, 04 Feb 2004 01:32:54 -0500 (EST)
- Subject: [patch] tm.texi: Replace SETUP_INCOMING_VARARGS withTARGET_SETUP_INCOMING_VARARGS.
Hi,
Committed as obvious.
Kazu Hirata
2004-02-04 Kazu Hirata <kazu@cs.umass.edu>
* doc/tm.texi: Replace SETUP_INCOMING_VARARGS with
TARGET_SETUP_INCOMING_VARARGS.
Index: tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.291
diff -u -r1.291 tm.texi
--- tm.texi 4 Feb 2004 06:07:39 -0000 1.291
+++ tm.texi 4 Feb 2004 06:28:23 -0000
@@ -4395,7 +4395,7 @@
Use this built-in function to save the argument registers in memory so
that the varargs mechanism can access them. Both ISO and traditional
versions of @code{va_start} must use @code{__builtin_saveregs}, unless
-you use @code{SETUP_INCOMING_VARARGS} (see below) instead.
+you use @code{TARGET_SETUP_INCOMING_VARARGS} (see below) instead.
On some machines, @code{__builtin_saveregs} is open-coded under the
control of the target hook @code{TARGET_EXPAND_BUILTIN_SAVEREGS}. On
@@ -4525,7 +4525,7 @@
@code{TARGET_SETUP_INCOMING_VARARGS}, but the other works like neither
@code{TARGET_SETUP_INCOMING_VARARGS} nor @code{TARGET_STRICT_ARGUMENT_NAMING} was
defined, then define this hook to return @code{true} if
-@code{SETUP_INCOMING_VARARGS} is used, @code{false} otherwise.
+@code{TARGET_SETUP_INCOMING_VARARGS} is used, @code{false} otherwise.
Otherwise, you should not define this hook.
@end deftypefn