This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] doc/*.texi: Don't mention deprecated target macros.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc-patches at gcc dot gnu dot org
- Date: Wed, 04 Feb 2004 00:36:08 -0500 (EST)
- Subject: [patch] doc/*.texi: Don't mention deprecated target macros.
Hi,
Committed as obvious to both 3.4 branch and mainline.
Kazu Hirata
2004-02-04 Kazu Hirata <kazu@cs.umass.edu>
* doc/interface.texi, doc/tm.texi, doc/trouble.texi: Don't
mention deprecated target macros.
Index: interface.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/interface.texi,v
retrieving revision 1.4
diff -u -r1.4 interface.texi
--- interface.texi 18 Jan 2004 01:20:46 -0000 1.4
+++ interface.texi 4 Feb 2004 05:28:40 -0000
@@ -28,8 +28,8 @@
values. (GCC typically allocates variables of such types in
registers also.) Structures and unions of other sizes are returned by
storing them into an address passed by the caller (usually in a
-register). The machine-description macros @code{STRUCT_VALUE} and
-@code{STRUCT_INCOMING_VALUE} tell GCC where to pass this address.
+register). The target hook @code{TARGET_STRUCT_VALUE_RTX}
+tells GCC where to pass this address.
By contrast, PCC on most target machines returns structures and unions
of any size by copying the data into an area of static storage, and then
Index: tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.289
diff -u -r1.289 tm.texi
--- tm.texi 31 Jan 2004 17:31:40 -0000 1.289
+++ tm.texi 4 Feb 2004 05:28:47 -0000
@@ -3873,7 +3873,7 @@
@code{FUNCTION_VALUE} is not used for return vales with aggregate data
types, because these are returned in another way. See
-@code{STRUCT_VALUE_REGNUM} and related macros, below.
+@code{TARGET_STRUCT_VALUE_RTX} and related macros, below.
@end defmac
@defmac FUNCTION_OUTGOING_VALUE (@var{valtype}, @var{func})
@@ -3891,7 +3891,7 @@
@code{FUNCTION_OUTGOING_VALUE} is not used for return vales with
aggregate data types, because these are returned in another way. See
-@code{STRUCT_VALUE_REGNUM} and related macros, below.
+@code{TARGET_STRUCT_VALUE_RTX} and related macros, below.
@end defmac
@defmac LIBCALL_VALUE (@var{mode})
Index: trouble.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/trouble.texi,v
retrieving revision 1.18
diff -u -r1.18 trouble.texi
--- trouble.texi 18 Jan 2004 11:57:17 -0000 1.18
+++ trouble.texi 4 Feb 2004 05:28:48 -0000
@@ -615,8 +615,8 @@
1, 2, 4 or 8 bytes long is returned like a scalar. A structure or union
with any other size is stored into an address supplied by the caller
(usually in a special, fixed register, but on some machines it is passed
-on the stack). The machine-description macros @code{STRUCT_VALUE} and
-@code{STRUCT_INCOMING_VALUE} tell GCC where to pass this address.
+on the stack). The target hook @code{TARGET_STRUCT_VALUE_RTX}
+tells GCC where to pass this address.
By contrast, PCC on most target machines returns structures and unions
of any size by copying the data into an area of static storage, and then