interface.texi, [...]: Don't mention deprecated target macros.

	* doc/interface.texi, doc/tm.texi, doc/trouble.texi: Don't
	mention deprecated target macros.

From-SVN: r77217

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 2c62f0142fb1d7576c963c908b436dd0c653ffc4..fd9c7f074e38bd5421c4373e5932f3e673fe56e7 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2004-02-04  Kazu Hirata  <kazu@cs.umass.edu>
+
+       * doc/interface.texi, doc/tm.texi, doc/trouble.texi: Don't
+       mention deprecated target macros.
+
 2004-02-04  Kazu Hirata  <kazu@cs.umass.edu>
 
        * config.gcc: Remove obsolete ports and configurations.

diff --git a/gcc/doc/interface.texi b/gcc/doc/interface.texi
index 262a4efb8f960996fd67db2837eb937d1d009c54..b55293d863c51d096c0a91870aac348b885e9471 100644 (file)
--- a/gcc/doc/interface.texi
+++ b/gcc/doc/interface.texi
@@ -28,8 +28,8 @@ long in the same registers used for @code{int} or @code{double} return
 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

diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index fe43af94e0503cefa573e581a3033ee63cde2486..d41a5861bef3232c7e684e02ba37fd2f4d4b1629 100644 (file)
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -3873,7 +3873,7 @@ known.
 
 @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 @@ If @code{FUNCTION_OUTGOING_VALUE} is not defined,
 
 @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})

diff --git a/gcc/doc/trouble.texi b/gcc/doc/trouble.texi
index 5ee77635f25e54a0d27fb0595e20969c5b7bf0e9..ce62c9536e3618ee05e875785e95ef4cac402357 100644 (file)
--- a/gcc/doc/trouble.texi
+++ b/gcc/doc/trouble.texi
@@ -615,8 +615,8 @@ The method used by GCC is as follows: a structure or union which is
 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