diff options
| -rw-r--r-- | gcc/ChangeLog | 7 | ||||
| -rw-r--r-- | gcc/config/arc/arc.h | 27 | ||||
| -rw-r--r-- | gcc/config/fr30/fr30.h | 28 | ||||
| -rw-r--r-- | gcc/doc/tm.texi | 6 |
4 files changed, 10 insertions, 58 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e67f9db0286..52e98f14f2b 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,5 +1,12 @@ 2004-02-04 Kazu Hirata <kazu@cs.umass.edu> + * config/arc/arc.h, config/fr30/fr30.h + (SETUP_INCOMING_VARARGS): Remove the target-independent + comments. + * doc/tm.texi: Don't mention deprecated target macros. + +2004-02-04 Kazu Hirata <kazu@cs.umass.edu> + * config/fr30/fr30.h (FUNCTION_VALUE): Remove the target-independent comment. diff --git a/gcc/config/arc/arc.h b/gcc/config/arc/arc.h index 5171849fcbe..bd0992c832d 100644 --- a/gcc/config/arc/arc.h +++ b/gcc/config/arc/arc.h @@ -732,33 +732,6 @@ FUNCTION_ARG_PASS_BY_REFERENCE ((CUM), (MODE), (TYPE), (NAMED)) ? PARM_BOUNDARY \ : 2 * PARM_BOUNDARY) -/* This macro offers an alternative - to using `__builtin_saveregs' and defining the macro - `EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous register - arguments into the stack so that all the arguments appear to have - been passed consecutively on the stack. Once this is done, you - can use the standard implementation of varargs that works for - machines that pass all their arguments on the stack. - - The argument ARGS_SO_FAR is the `CUMULATIVE_ARGS' data structure, - containing the values that obtain after processing of the named - arguments. The arguments MODE and TYPE describe the last named - argument--its machine mode and its data type as a tree node. - - The macro implementation should do two things: first, push onto the - stack all the argument registers *not* used for the named - arguments, and second, store the size of the data thus pushed into - the `int'-valued variable whose name is supplied as the argument - PRETEND_SIZE. The value that you store here will serve as - additional offset for setting up the stack frame. - - If the argument NO_RTL is nonzero, it means that the - arguments of the function are being analyzed for the second time. - This happens for an inline function, which is not actually - compiled until the end of the source file. The macro - `SETUP_INCOMING_VARARGS' should not generate any instructions in - this case. */ - #define SETUP_INCOMING_VARARGS(ARGS_SO_FAR, MODE, TYPE, PRETEND_SIZE, NO_RTL) \ arc_setup_incoming_varargs(&ARGS_SO_FAR, MODE, TYPE, &PRETEND_SIZE, NO_RTL) diff --git a/gcc/config/fr30/fr30.h b/gcc/config/fr30/fr30.h index 2a4a886de45..8c9841d9b83 100644 --- a/gcc/config/fr30/fr30.h +++ b/gcc/config/fr30/fr30.h @@ -848,34 +848,6 @@ enum reg_class /*}}}*/ /*{{{ Implementing the VARARGS Macros. */ -/* This macro offers an alternative to using `__builtin_saveregs' and defining - the macro `EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous register - arguments into the stack so that all the arguments appear to have been - passed consecutively on the stack. Once this is done, you can use the - standard implementation of varargs that works for machines that pass all - their arguments on the stack. - - The argument ARGS_SO_FAR is the `CUMULATIVE_ARGS' data structure, containing - the values that obtain after processing of the named arguments. The - arguments MODE and TYPE describe the last named argument--its machine mode - and its data type as a tree node. - - The macro implementation should do two things: first, push onto the stack - all the argument registers *not* used for the named arguments, and second, - store the size of the data thus pushed into the `int'-valued variable whose - name is supplied as the argument PRETEND_ARGS_SIZE. The value that you - store here will serve as additional offset for setting up the stack frame. - - Because you must generate code to push the anonymous arguments at compile - time without knowing their data types, `SETUP_INCOMING_VARARGS' is only - useful on machines that have just a single category of argument register and - use it uniformly for all data types. - - If the argument SECOND_TIME is nonzero, it means that the arguments of the - function are being analyzed for the second time. This happens for an inline - function, which is not actually compiled until the end of the source file. - The macro `SETUP_INCOMING_VARARGS' should not generate any instructions in - this case. */ #define SETUP_INCOMING_VARARGS(ARGS_SO_FAR, MODE, TYPE, PRETEND_ARGS_SIZE, SECOND_TIME) \ if (! SECOND_TIME) \ fr30_setup_incoming_varargs (ARGS_SO_FAR, MODE, TYPE, & PRETEND_ARGS_SIZE) diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index d41a5861bef..cb32cc38acd 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -4398,9 +4398,9 @@ versions of @code{va_start} must use @code{__builtin_saveregs}, unless you use @code{SETUP_INCOMING_VARARGS} (see below) instead. On some machines, @code{__builtin_saveregs} is open-coded under the -control of the macro @code{EXPAND_BUILTIN_SAVEREGS}. On other machines, -it calls a routine written in assembler language, found in -@file{libgcc2.c}. +control of the target hook @code{TARGET_EXPAND_BUILTIN_SAVEREGS}. On +other machines, it calls a routine written in assembler language, +found in @file{libgcc2.c}. Code generated for the call to @code{__builtin_saveregs} appears at the beginning of the function, as opposed to where the call to |